From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [stable] PA-RISC: compile error in include/net/dst.h
Date: Tue, 24 May 2011 21:19:45 +0200 [thread overview]
Message-ID: <1490722.55WlhWHEVK@donald.sf-tec.de> (raw)
In-Reply-To: <20110524190614.GA25820@hiauly1.hia.nrc.ca>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Am Dienstag, 24. Mai 2011, 15:06:14 schrieb John David Anglin:
> On Tue, 24 May 2011, Rolf Eike Beer wrote:
> > As 2.6.38.6 does if I use the correct .config. So it is an older issue
> > which is not related to recent changes but likely some general HPPA
> > breakage. We'll discuss the rest on linux-parisc.
>
> If you believe this is a compiler error, I suggest using gcc 4.5.3 or
> 4.6.0.
>
> All releases prior to 4.5.2 contain bugs in delay slot optimization
> resulting in incorrect register liveness.
If you think of PR46915: I was the one that originally stumbled over this
although GM took the hard work of bisecting and reporting that upstream. As I
said before, the compiler is 4.5.2.
And: no, I don't suspect a compiler error. Only a .config screwup. I'm
currently trying to find the culprit. Good luck it breaks rather early in the
compile.
To reproduce try to compile for hppa64 with default .config, this seems what
has happened to me.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-24 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 8:15 PA-RISC: compile error in include/net/dst.h Rolf Eike Beer
2011-05-22 14:13 ` WANG Cong
2011-05-22 14:32 ` [stable] " Greg KH
2011-05-22 22:29 ` Rolf Eike Beer
2011-05-24 18:37 ` Rolf Eike Beer
2011-05-24 19:06 ` [stable] " John David Anglin
2011-05-24 19:19 ` Rolf Eike Beer [this message]
2011-05-24 19:47 ` Rolf Eike Beer
2011-05-24 20:49 ` John David Anglin
2011-05-24 20:59 ` Rolf Eike Beer
2011-05-24 21:10 ` John David Anglin
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=1490722.55WlhWHEVK@donald.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.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