All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bradley D. LaRonde" <brad@laronde.org>
To: <linux-mips@linux-mips.org>,
	"Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: [PATCH] catch "new" gcc 3.4.0 sections
Date: Tue, 13 Apr 2004 15:43:39 -0400	[thread overview]
Message-ID: <02ea01c4218f$9ea240d0$8d01010a@prefect> (raw)
In-Reply-To: 20040413193158.GO27939@rembrandt.csv.ica.uni-stuttgart.de

----- Original Message ----- 
From: "Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
To: <linux-mips@linux-mips.org>
Sent: Tuesday, April 13, 2004 3:31 PM
Subject: Re: [PATCH] catch "new" gcc 3.4.0 sections


> Bradley D. LaRonde wrote:
> > Building with gcc 3.4.0 emits a couple new sections, .rodata.cst4 and
> > .rodata.str1.4, which the current ld.script doesn't contemplate.  Here
is a
> > patch to catch them (and maybe some other latent ones).
> >
> > Anyone know why or when these sections are emitted?
>
> I'd guess to keep differently aligned strings in separate sections,
> as a preliminary for improved string merging.
>
> > Regards,
> > Brad
> >
> >
> > diff -u -r1.1.1.1 ld.script.in
> > --- arch/mips/ld.script.in      10 Nov 2003 21:06:52 -0000      1.1.1.1
> > +++ arch/mips/ld.script.in      13 Apr 2004 19:18:25 -0000
> > @@ -11,6 +11,11 @@
> >      *(.text)
> >      *(.rodata)
> >      *(.rodata1)
> > +    *(.rodata.str1.1);
> > +    *(.rodata.str1.4);
> > +    *(.rodata.str1.32);
> > +    *(.rodata.cst4);
> > +    *(.rodata.cst8);
>
> Why not just *(.rodata*); ?

I dunno.  There is already a tradition with .rodata and .rodata1 being
listed separately.  Maybe to spy on future gcc behavior?


Regards,
Brad

WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@laronde.org>
To: linux-mips@linux-mips.org,
	Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: [PATCH] catch "new" gcc 3.4.0 sections
Date: Tue, 13 Apr 2004 15:43:39 -0400	[thread overview]
Message-ID: <02ea01c4218f$9ea240d0$8d01010a@prefect> (raw)
Message-ID: <20040413194339.VOzMfyACLZKHmoWBt-ni532np9vnpml6Sffkx5QtYmE@z> (raw)
In-Reply-To: 20040413193158.GO27939@rembrandt.csv.ica.uni-stuttgart.de

----- Original Message ----- 
From: "Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
To: <linux-mips@linux-mips.org>
Sent: Tuesday, April 13, 2004 3:31 PM
Subject: Re: [PATCH] catch "new" gcc 3.4.0 sections


> Bradley D. LaRonde wrote:
> > Building with gcc 3.4.0 emits a couple new sections, .rodata.cst4 and
> > .rodata.str1.4, which the current ld.script doesn't contemplate.  Here
is a
> > patch to catch them (and maybe some other latent ones).
> >
> > Anyone know why or when these sections are emitted?
>
> I'd guess to keep differently aligned strings in separate sections,
> as a preliminary for improved string merging.
>
> > Regards,
> > Brad
> >
> >
> > diff -u -r1.1.1.1 ld.script.in
> > --- arch/mips/ld.script.in      10 Nov 2003 21:06:52 -0000      1.1.1.1
> > +++ arch/mips/ld.script.in      13 Apr 2004 19:18:25 -0000
> > @@ -11,6 +11,11 @@
> >      *(.text)
> >      *(.rodata)
> >      *(.rodata1)
> > +    *(.rodata.str1.1);
> > +    *(.rodata.str1.4);
> > +    *(.rodata.str1.32);
> > +    *(.rodata.cst4);
> > +    *(.rodata.cst8);
>
> Why not just *(.rodata*); ?

I dunno.  There is already a tradition with .rodata and .rodata1 being
listed separately.  Maybe to spy on future gcc behavior?


Regards,
Brad

  reply	other threads:[~2004-04-13 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 19:20 [PATCH] catch "new" gcc 3.4.0 sections Bradley D. LaRonde
2004-04-13 19:20 ` Bradley D. LaRonde
2004-04-13 19:31 ` Thiemo Seufer
2004-04-13 19:43   ` Bradley D. LaRonde [this message]
2004-04-13 19:43     ` Bradley D. LaRonde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='02ea01c4218f$9ea240d0$8d01010a@prefect' \
    --to=brad@laronde.org \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.