Skip to contentSkip to conversation

gcc-4.2-hppa64 bug

DISCUSSION Kyle McMartin 3 participants 5 messages Dec 5, 2007

lore
Share & tools
lore

Kyle McMartin

author
#0 lore raw

John et al,

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.

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?

make fs/ocfs2/ocfs2.ko:
!SMP SMP
32-bit y y
64-bit y fails

The troublesome source file appears to be fs/ocfs2/alloc.o, the rest seem to build fine.

cheers,
Kyle

author
#1 lore raw
Quoted 3 lines · Kyle McMartin

The troublesome source file appears to be fs/ocfs2/alloc.o, the rest seem to build fine.

Randolph pointed out the "-da" argument to me, the last pass it makes it to is alloc.c.160r.shorten.

I'll leave this one going to check for forward progress as well.

cheers,
Kyle

#2 lore raw
In reply to Kyle McMartin
Quoted 3 lines

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?

The general process is to determine the compilation command that fails. "-da" can be used to determine the last function that's being compiled. Then, try to whittle down the testcase to something that's easier to debug. That's a good point to submit a GCC PR.

To actually debug the compilation, use "-v" to see the command gcc uses to run cc1. Run cc1 under gdb with the arguments shown with "-v". However, you probably won't get very far without a version of cc1 with debug symbols. It's also easiest to debug cc1 from stage1 of the GCC bootstrap.

Dave

Signature · 2 lines
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
#3 lore raw
In reply to Kyle McMartin

Kyle McMartin a =E9crit :

Quoted 10 lines

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?

Quoted 8 lines

=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
 `. `'   [email protected]         | [email protected]
   `-    people.debian.org/~aurel32 | www.aurel32.net

--=20
To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]= .org