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)




The variables are:

unlikely_section_label
hot_section_label
cold_section_end_label
hot_section_end_label

They are used in assemble_start_function and assemble_end_function,
where they are written out.  They are also used in dbxout.c and
dwarf2out.c, where they are used to calculate the sizes of the text
sections for the debugging information.

-- Caroline
ctice@apple.com

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

Caroline Tice <ctice@apple.com> writes:

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?

Where are these global variables used?


Yes, in general having random routines depend on the contents of
random global variables is a bad idea.



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