From: Aurelien Jarno <aurelien@aurel32.net>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: linux-parisc@vger.kernel.org, debian-hppa@lists.debian.org
Subject: Re: gcc-4.2-hppa64 bug
Date: Wed, 05 Dec 2007 20:19:14 +0100 [thread overview]
Message-ID: <4756F9B2.8050105@aurel32.net> (raw)
In-Reply-To: <20071205170219.GA3608@fattire.cabal.ca>
Kyle McMartin a =E9crit :
> John et al,
>=20
> We're currently hitting a gcc bug on hppa64 with both gcc-4.1 and
> gcc-4.2. Symptoms are that a build of the ocfs2 module spins
> (apparently) forever, I'm leaving a copy building to see if it
> eventually makes forward progress.
>=20
> It's pretty easily reproduceable by building a modular kernel with the
> ocfs2 module enabled. Is there anything I can do to help narrow this
> down?
>=20
> make fs/ocfs2/ocfs2.ko:
> !SMP SMP
> 32-bit y y
> 64-bit y fails
>=20
> The troublesome source file appears to be fs/ocfs2/alloc.o, the rest
> seem to build fine.
Please note that this bug has been reported sometimes ago in the
upstream bug tracker. See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D=
31944
Cheers,
Aurelien
--=20
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--=20
To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian=
.org
next prev parent reply other threads:[~2007-12-05 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 17:02 gcc-4.2-hppa64 bug Kyle McMartin
2007-12-05 18:02 ` Kyle McMartin
2007-12-05 19:15 ` John David Anglin
2007-12-05 19:19 ` Aurelien Jarno [this message]
2007-12-05 20:34 ` 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=4756F9B2.8050105@aurel32.net \
--to=aurelien@aurel32.net \
--cc=debian-hppa@lists.debian.org \
--cc=kyle@mcmartin.ca \
--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