This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: AIX bootstrap failure (was Re: Hot/cold partitioning fixes)


I was thinking that since I already have global variables that I was putting the old
strings into, I would just use those global variables putting the result of
calling ASM_GENERATE_INTERNAL_LABLE into them. Is this a bad idea? Should
I attach them to the function structure instead?


-- Caroline

On Apr 1, 2005, at 2:07 PM, Geoffrey Keating wrote:

Daniel Jacobowitz <drow@false.org> writes:

On Fri, Apr 01, 2005 at 12:00:08PM -0800, Caroline Tice wrote:
I really need labels with predictable names, as these labels are used in
the debugging information to determine the size of the text sections.

And you can't somehow associate the labels with the function? For instance, record them in "struct function", or as a property of the FUNCTION_DECL. It looks like current_function isn't usable during dwarf2 output, but you'll have the decl; you could create a hash table mapping the FUNCTION_DECL to the appropriate label.

They should go in 'struct function'. There's a pointer to the function structure from the DECL.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]