public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at bigpond dot net dot au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/37739] [4.4 Regression] bootstrap broken with core gcc > gcc-4.2.x
Date: Fri, 03 Jul 2009 01:38:00 -0000 [thread overview]
Message-ID: <20090703013846.23699.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37739-5406@http.gcc.gnu.org/bugzilla/>
------- Comment #18 from amodra at bigpond dot net dot au 2009-07-03 01:38 -------
I wonder whether people reporting that this bug has not been fixed (at least
for C/C++) realize that the fix needs to be in the sources you are building.
It's not a fix that affects the installed compiler.
I've resisted turning on relax by default in ld because it slows down link time
due to adding another pass over the relocations in input files. I probably
should look at doing something clever in ld. A neat trick would be to
automatically turn on relax if executable sections have addresses that might
result in reloc overflow.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37739
next prev parent reply other threads:[~2009-07-03 1:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 19:19 [Bug bootstrap/37739] New: " andreast at gcc dot gnu dot org
2008-10-05 19:27 ` [Bug bootstrap/37739] " andreast at gcc dot gnu dot org
2008-10-05 21:55 ` schwab at suse dot de
2008-10-06 21:16 ` [Bug bootstrap/37739] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-10-06 21:54 ` pinskia at gcc dot gnu dot org
2008-10-22 3:31 ` mmitchel at gcc dot gnu dot org
2008-11-14 15:11 ` jakub at gcc dot gnu dot org
2008-11-16 13:04 ` jakub at gcc dot gnu dot org
2008-12-11 10:03 ` jakub at gcc dot gnu dot org
2008-12-11 11:30 ` rguenth at gcc dot gnu dot org
2008-12-11 16:35 ` jakub at gcc dot gnu dot org
2008-12-15 19:36 ` andreast at gcc dot gnu dot org
2008-12-19 14:58 ` jakub at gcc dot gnu dot org
2008-12-19 15:04 ` jakub at gcc dot gnu dot org
2009-02-11 18:14 ` lucier at math dot purdue dot edu
2009-06-11 0:01 ` mikpe at it dot uu dot se
2009-06-14 9:27 ` acrux at linuxmail dot org
2009-07-02 16:26 ` jan at codejunky dot org
2009-07-02 16:36 ` lucier at math dot purdue dot edu
2009-07-02 16:49 ` bergner at gcc dot gnu dot org
2009-07-03 1:38 ` amodra at bigpond dot net dot au [this message]
2009-07-19 17:04 ` rguenth at gcc dot gnu dot org
2009-07-19 19:23 ` rguenth at gcc dot gnu dot org
2009-07-19 19:24 ` rguenth at gcc dot gnu dot org
2009-07-22 17:21 ` giffordj at la dot twcbc dot com
2009-07-23 13:37 ` jakub at gcc dot gnu dot org
2009-07-23 16:51 ` giffordj at la dot twcbc dot com
2009-07-23 16:56 ` jakub at gcc dot gnu dot org
2009-07-23 18:36 ` giffordj at la dot twcbc dot com
2009-07-24 9:47 ` jakub at gcc dot gnu dot org
2009-07-24 13:12 ` giffordj at la dot twcbc dot com
2009-07-26 20:28 ` giffordj at la dot twcbc dot com
2009-08-06 17:32 ` giffordj at la dot twcbc dot com
2009-08-11 15:10 ` giffordj at la dot twcbc dot com
2009-08-31 21:48 ` mmitchel at gcc dot gnu dot org
2009-09-30 2:29 ` amodra at bigpond dot net dot au
2009-10-07 13:35 ` jakub at gcc dot gnu dot org
2009-10-07 19:55 ` andreast at gcc dot gnu dot org
2009-10-07 22:35 ` amodra at bigpond dot net dot au
2009-10-08 5:10 ` andreast at gcc dot gnu dot org
2010-06-07 8:40 ` rguenth at gcc dot gnu dot org
[not found] <bug-37739-4@http.gcc.gnu.org/bugzilla/>
2012-01-28 5:17 ` pinskia at gcc dot gnu.org
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=20090703013846.23699.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).