(original) (raw)

Hi Muhui,

In general the function's start address would be the low\_pc. From time to time I hear about people wanting to put cold code blocks before the entry point; I think so far that has not been implemented, but if it is, then low\_pc would be the lowest code address in the function and DW\_AT\_entry\_pc would record the entrypoint address.

Regarding multi-entry functions, I'm aware of two cases where this occurs in a source language. One is when you have optional parameters in C++, which effectively creates one or more overloads for the function; the other is PL/I which allows defining an entry label within the body of the function. For the C++ case, I'd expect the front-end to create stubs that fill in the defaulted parameters and then tail-call the main function; in this case, each stub would have its own debug-info entry and be treated as its own independent function for debug-info purposes. For PL/I, I would probably do the same, although I admit it has been a long time since I did any PL/I programming and I never worked on a PL/I compiler.

If I am not covering the cases you are interested in, please provide more details.

Thanks,

--paulr