Bug 25853

Summary:	Cannot compile WindowMaker--0.92.0 in FC4: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'
Product:	gcc	Reporter:	backes
Component:	target	Assignee:	Not yet assigned to anyone <unassigned>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	backes, bero, ffelix, gcc-bugs, jakub, jbernardo, mark, martin.drab, michaelni, mikulas, pawel_sikora, stian, weimer
Priority:	P3
Version:	4.2.0
Target Milestone:	---
Host:		Target:
Build:		Known to work:
Known to fail:		Last reconfirmed:
Attachments:	faulty source

Description backes 2006-01-19 06:45:23 UTC

I downloaded the WindowMaker-0.92.0.tar.gz and tried to compile it under FedoraCore4, AMD XP 3200+.

The compilation breaks with the following error message:
gmake[1]: Entering directory `/tmp/WindowMaker-0.92.0/wrlib'
Making all in .
gmake[2]: Entering directory `/tmp/WindowMaker-0.92.0/wrlib'
`echo /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../src  -I/usr/local/include  -I/usr/X11R6/include    -g -O2 | sed -e s/-fomit-frame-pointer//` -O0 -c x86_specific.c
 gcc -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -O0 -c x86_specific.c  -fPIC -DPIC -o .libs/x86_specific.o
x86_specific.c: In function 'x86_mmx_TrueColor_32_to_16':
x86_specific.c:107: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm'
gmake[2]: *** [x86_specific.lo] Error 1
gmake[2]: Leaving directory `/tmp/WindowMaker-0.92.0/wrlib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/tmp/WindowMaker-0.92.0/wrlib'
gmake: *** [all-recursive] Error 1

...

Comment 1 Andrew Pinski 2006-01-19 06:50:05 UTC

This is an error but not always a bug in GCC.  It is most likely a bug in the WindowMaker source.
Can you attach the preprocessed source?

Comment 2 backes 2006-01-19 07:36:45 UTC

Created attachment 10671 [details]
faulty source

It seems to be an error in the source.

Comment 3 backes 2006-01-19 08:53:06 UTC

I will report it to the WindowMaker developpers. You may close the bag.

Comment 4 Andrew Pinski 2006-01-19 12:38:03 UTC

Yes this is a dup of the closed (invalid) bug 11203.

*** This bug has been marked as a duplicate of 11203 ***