public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tim Van Holder <tim.van.holder@pandora.be>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3867: [djgpp] eh_frame optimization check in configure is broken
Date: Sat, 30 Nov 2002 14:35:00 -0000	[thread overview]
Message-ID: <20021121080601.17997.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/3867; it has been noted by GNATS.

From: Tim Van Holder <tim.van.holder@pandora.be>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/3867: [djgpp] eh_frame optimization check in
	configure is broken
Date: 21 Nov 2002 08:58:15 +0100

 It's not a failure as such - configure merely finds the eh_frame
 optimization bug when it is not present.
 This is still the case in gcc 3.2; configure.in contains a piece
 of assembler code that uses .4byte and multiple arguments for
 .section.  Even when binutils 2.13 is used, those are NOT
 supported for coff targets (djgpp, mingw32), causing as to
 fail, and configure to assume the test failed.
 Using .long instead of .4byte and removing the extra arguments
 to .section results in an assembler file that gives the proper
 results for coff as well as ELF.
 
 The check for the linker's eh_frame header optimization is even
 more broken for those platforms, as it checks 4- and 8-byte
 alignments (using .${gc_WS}byte as pseudo-op); in that test it
 is not possible to simply replace .4byte by .long.
 
 Perhaps this is a binutils issue (perhaps as should treat .4byte
 as a synonym for .long for a COFF target, and silently ignore
 extra arguments for .section), but this has been causing gcc to
 misdetect eh_frame stuff on COFF platforms for quite a while now.
 
 -- 
 Tim Van Holder <tim.van.holder@pandora.be>
 


             reply	other threads:[~2002-11-21  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 14:35 Tim Van Holder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 13:36 Tim Van Holder
2003-05-14  8:36 Dara Hazeghi
2002-11-27 10:36 bangerth

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=20021121080601.17997.qmail@sources.redhat.com \
    --to=tim.van.holder@pandora.be \
    --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).