From: Richard Sandiford <rsandifo@nildram.co.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Martin Michlmayr <tbm@cyrius.com>,
David Daney <ddaney@avtrex.com>,
MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: Gcc 4.2.2 broken for kernel builds
Date: Mon, 15 Oct 2007 17:19:18 +0100 [thread overview]
Message-ID: <87ve98ic55.fsf@firetop.home> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710151553200.16262@blysk.ds.pg.gda.pl> (Maciej W. Rozycki's message of "Mon\, 15 Oct 2007 15\:59\:51 +0100 \(BST\)")
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
> On Sat, 13 Oct 2007, Richard Sandiford wrote:
>> FWIW, I've added some notes about the underlying cause. I think this
>> could in principle happen with any gcc release.
>
> It has been seen with GCC 3.4 and IIRC SDE has a hack in binutils to
> disable this error as a workaround. I guess the problem has always been
> there since explicit relocs were added to GCC; it is just it hardly ever
> happens.
Agreed. And in options-speak, "explicit relocs" means both -mexplicit-relocs
and -msplit-addresses. The associated gas warning was disabled in the
initial revision of sourceware binutils:
1.1 (rth 03-May-99): #if 0 /* GCC code motion plus incomplete dead code elimination
1.1 (rth 03-May-99): can leave a %hi without a %lo. */
1.1 (rth 03-May-99): if (pass == 1)
1.1 (rth 03-May-99): as_warn_where (l->fixp->fx_file, l->fixp->fx_line,
1.1 (rth 03-May-99): _("Unmatched %%hi reloc"));
1.1 (rth 03-May-99): #endif
so I think this problem has been seen with GCC 2 as well as 3 and 4.
Richard
next prev parent reply other threads:[~2007-10-15 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 17:22 Gcc 4.2.2 broken for kernel builds Ralf Baechle
2007-10-12 17:48 ` David Daney
2007-10-12 17:53 ` Ralf Baechle
2007-10-12 18:33 ` David Daney
2007-10-12 18:49 ` Ralf Baechle
2007-10-12 19:14 ` Martin Michlmayr
2007-10-12 19:16 ` Ralf Baechle
2007-10-13 10:51 ` Richard Sandiford
2007-10-15 14:59 ` Maciej W. Rozycki
2007-10-15 16:19 ` Richard Sandiford [this message]
2007-10-24 19:46 ` Martin Michlmayr
2007-10-12 20:33 ` Martin Michlmayr
2007-10-12 18:45 ` Martin Michlmayr
2007-10-12 22:42 ` David Daney
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=87ve98ic55.fsf@firetop.home \
--to=rsandifo@nildram.co.uk \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tbm@cyrius.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