public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: chris@lslsun.epfl.ch (Christian Iseli)
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Named bss sections
Date: Tue, 09 Sep 1997 04:15:00 -0000	[thread overview]
Message-ID: <199709090933.LAA29452@lslsun17.epfl.ch> (raw)

> I'll ask my question another way :-)  Show me a variable declaration that
> specifies a specific section, but doesn't end up where it belongs and is
> fixed by your patch.

Ah, now I see it.  Turns out my target code uses ENCODE_SECTION_INFO to decide
if it wants to put some small variables in a special section.  The code I wrote
forgot to clear the DECL_COMMON flag after assigning the variable to a section.
Silly me... the patch is not needed now that my other code is corrected.

					Christian

             reply	other threads:[~1997-09-09  4:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-09  4:15 Christian Iseli [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-09-08  6:50 Christian Iseli
1997-09-08  7:58 ` Jeffrey A Law
1997-09-08 10:32 ` Martin Mares
1997-09-02  7:15 Christian Iseli
1997-09-02  9:18 ` Gavin Koch
1997-09-04 22:30 ` Jeffrey A Law

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=199709090933.LAA29452@lslsun17.epfl.ch \
    --to=chris@lslsun.epfl.ch \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).