public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8249: Objects moved from common to BSS with -fdata-sections
Date: Mon, 23 Dec 2002 09:36:00 -0000	[thread overview]
Message-ID: <20021223173601.31035.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8249; it has been noted by GNATS.

From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: bangerth@ticam.utexas.edu
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/8249: Objects moved from common to BSS with -fdata-sections
Date: Mon, 23 Dec 2002 11:27:02 -0600 (CST)

 In article <Pine.LNX.4.44.0212201110540.18379-100000@gandalf.ticam.utexas.edu>,
 Wolfgang Bangerth<bangerth@ticam.utexas.edu> writes:
 
 >> Knowing what Linux does might help me understand more about this
 >> problem.  Linux does properly support -fdata-sections, no?  In my
 >> case, the linker is GNU ld version 2.13 20020917 (and also tested with
 >> GNU ld version 2.12.1 [FreeBSD] 2002-07-20).
 
 > I have no idea how well Linux supports -fdata-sections. To be honest, I 
 > don't even know properly what this is about, I was just going through bug 
 > reports and checked whether they apply to my box as well and if I can 
 > contribute something :-)
 
 > GNU ld version 2.11.92.0.10 20011021 (SuSE)
 
 Thanks for checking.  Your machine got the same asm output file (at
 least in the section of interest), but the linker version is
 different.  Thus, I'd now say the bug is not in the compiler but in a
 change in the linker or bug in my port's ld configuration.
 
 Perhaps, we should close it with this analysis.
 
 Regards,
 Loren


             reply	other threads:[~2002-12-23 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23  9:36 Loren James Rittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-20  9:16 Wolfgang Bangerth
2002-12-19 21:36 Loren James Rittle
2002-12-19 17:22 bangerth
2002-10-17  3:46 rittle

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=20021223173601.31035.qmail@sources.redhat.com \
    --to=rittle@latour.rsch.comm.mot.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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 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).