> -----Original Message----- > From: Joseph Myers [mailto:jos...@codesourcery.com] > Sent: 24 October 2012 13:32 > To: Paulo Matos > Cc: gcc@gcc.gnu.org > Subject: RE: Documentation problem with TEXT_SECTION_ASM_OP > > I don't like this #else. Presumably the libgcc code already works if > TEXT_SECTION_ASM_OP isn't defined at all. So the equivalent is simply not > to define __LIBGCC_TEXT_SECTION_ASM_OP__ in that case, rather than > synthesizing a definition from other information. >
Let me add that I am not so sure about this. I arrived at this problem because I started defining text_section through TARGET_ASM_INIT_SECTIONS instead of TEXT_SECTION_ASM_OP and crtstuff.c started complaining during libgcc compile time that TEXT_SECTION_ASM_OP was not defined. I looked at most of the upstream backends and unfortunately none seem to not define TEXT_SECTION_ASM_OP even though according to the documents that's possible cause it allows you to define text_section through the TARGET_ASM_INIT_SECTIONS hook instead. Paulo Matos
