From: Richard Sandiford <rsandifo@nildram.co.uk>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: 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: Sat, 13 Oct 2007 11:51:04 +0100 [thread overview]
Message-ID: <87d4vj9tk7.fsf@firetop.home> (raw)
In-Reply-To: <20071012191645.GB4832@linux-mips.org> (Ralf Baechle's message of "Fri\, 12 Oct 2007 20\:16\:45 +0100")
Ralf Baechle <ralf@linux-mips.org> writes:
> On Fri, Oct 12, 2007 at 09:14:46PM +0200, Martin Michlmayr wrote:
>> > For the moment the receipe to reproduce is to checkout
>> > 7b94a571d6f31ac6303d62c2aafcae40b66f24a3 from the linux-mips.org kernel
>> > tree (that's on linux-2.6.18-stable) and build malta_defconfig with
>> > gcc 4.2.2 and binutils 2.17 or 2.18, both configured for mipsel-linux.
>>
>> Okay, I can see it. I'll submit a testcase.
>
> Thanks :-)
FWIW, I've added some notes about the underlying cause. I think this
could in principle happen with any gcc release.
Richard
next prev parent reply other threads:[~2007-10-13 10:51 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 [this message]
2007-10-15 14:59 ` Maciej W. Rozycki
2007-10-15 16:19 ` Richard Sandiford
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=87d4vj9tk7.fsf@firetop.home \
--to=rsandifo@nildram.co.uk \
--cc=ddaney@avtrex.com \
--cc=linux-mips@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