Re: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo J. Matos
On 24/10/12 17:30, Joseph S. Myers wrote: On Wed, 24 Oct 2012, Paulo Matos wrote: Conversions of target macros to hooks are generally of interest. I don't think we want a stream-of-consciousness sequence of messages about successive aspects of the issue. I apologize if my messages became a nu

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Joseph S. Myers
On Wed, 24 Oct 2012, Paulo Matos wrote: > Are these changes to handling of TEXT_SECTION_ASM_OP interesting for > GCC? If they are I will look further into improving the code and turning > it into a patch. Conversions of target macros to hooks are generally of interest. I don't think we want a

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo Matos
> -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

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo Matos
> -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

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo Matos
> -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 > > On Wed, 24 Oct 2012, Paulo Matos wrote: &g

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Joseph S. Myers
On Wed, 24 Oct 2012, Paulo Matos wrote: > I gave it a go with TEXT_SECTION_ASM_OP. Given what you've found, maybe other macros are easier to convert > I started by changing crtstuff.c to use __LIBGCC_TEXT_SECTION_ASM_OP__ > instead of TEXT_SECTION_ASM_OP. I noticed crtstuff.c is not compile

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo Matos
> -Original Message- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Joseph S. Myers > Sent: 23 October 2012 15:28 > To: Paulo Matos > Cc: gcc@gcc.gnu.org > Subject: Re: Documentation problem with TEXT_SECTION_ASM_OP > > conversions

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-24 Thread Paulo Matos
> -Original Message- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Joseph S. Myers > Sent: 23 October 2012 15:28 > To: Paulo Matos > Cc: gcc@gcc.gnu.org > Subject: Re: Documentation problem with TEXT_SECTION_ASM_OP > > So far only

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-23 Thread Joseph S. Myers
On Tue, 23 Oct 2012, Paulo Matos wrote: > If this -fbuilding-libgcc being passed at current HEAD? I am looking at > 4.7 and no flag like that Is being passed while building libgcc. It's in LIBGCC2_CFLAGS in libgcc/Makefile.in in both 4.7 and trunk. -- Joseph S. Myers jos...@codesourcery.com

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-23 Thread Paulo Matos
> -Original Message- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Joseph S. Myers > Sent: 23 October 2012 15:28 > To: Paulo Matos > Cc: gcc@gcc.gnu.org > Subject: Re: Documentation problem with TEXT_SECTION_ASM_OP > > At &

Re: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-23 Thread Joseph S. Myers
On Tue, 23 Oct 2012, Paulo Matos wrote: > Since this is most likely a problem with the docs, how can I achieve > something like this and have only a string literal as value or > TEXT_SECTION_ASM_OP? At I listed this macro, and lots of others

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-23 Thread Paulo Matos
> -Original Message- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Paulo Matos > Sent: 23 October 2012 14:47 > To: gcc@gcc.gnu.org > Subject: RE: Documentation problem with TEXT_SECTION_ASM_OP > > This sentence is quite confusing. &

RE: Documentation problem with TEXT_SECTION_ASM_OP

2012-10-23 Thread Paulo Matos
I just noticed at the top of Sections.html in gccint: The normal way of controlling a foo_section variable is to define the associated FOO_SECTION_ASM_OP macro, as described below. The macros are only read once, when varasm.c initializes itself, so their values must be run-time constants. This