Compiler error while compiling XFree86-3.9.17

2000-02-01 Thread Theo van Klaveren


I received the following compiler error while compiling the XFree86-3.9.17
snapshot on a (very) fresh -CURRENT system:

-- begin cut'n'paste --

cc -c -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith 
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations 
-Wredundant-decls -Wnested-externs -I. -I.-I../../../include/fonts -I../mi 
-I../../../programs/Xserver/hw/xfree86/common -I../../../include/fonts
-I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE  -DXKB -DLBX
-DXAPPGROUP -DXCSECURITY -DTOGCUP  -DXF86BIGFONT -DDPMSExtension  -DPIXPRIV
-DPANORAMIX  -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH 
-DXFreeXDGA -DXvExtension -DXFree86LOADER  -DXFree86Server -DXF86VIDMODE 
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15
-DNARROWPROTO xf86vmode.c
In file included from xf86vmode.c:41:
../include/extnsionst.h:91: warning: function declaration isn't a
prototype
../include/extnsionst.h:100: warning: function declaration isn't a
prototype
../include/extnsionst.h:106: warning: function declaration isn't a
prototype
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 300 298 302 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
Stop in /usr/home/havoc/Build/xc/programs/Xserver/Xext.

-- end cut'n'paste --

I assume this is a compiler bug. Is there a workaround or a patch 
available for the system compiler or should I install the gcc-devel port
(for which I probably don't have enough disk space, but oh well)?

/^\ | Theo van Klaveren   [EMAIL PROTECTED]
 /^\\_//^\  | http://phoenix.student.utwente.nl ICQ #1353681
 \_/-|-\_/  |
/   |  This email was powered by FreeBSD
   
`He's the mad scientist, and I'm his beautiful daughter.'
- opening sentence from Heinlein's 'The number of the beast'



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Compiler error while compiling XFree86-3.9.17

2000-02-01 Thread Chris Piazza

On Tue, Feb 01, 2000 at 03:30:36PM +0100, Theo van Klaveren wrote:
 
 I received the following compiler error while compiling the XFree86-3.9.17
 snapshot on a (very) fresh -CURRENT system:
 
 -- begin cut'n'paste --
 
  -- snip cut'n'paste --
   ...errors...
 
 -- end cut'n'paste --
 
 I assume this is a compiler bug. Is there a workaround or a patch 
 available for the system compiler or should I install the gcc-devel port
 (for which I probably don't have enough disk space, but oh well)?

The workaround is to compile the file that's dying with no optimisations.
It compiles fine without them... sorry I don't have a patch handy.

-Chris
-- 
[EMAIL PROTECTED]   [EMAIL PROTECTED]
Abbotsford, BC, Canada


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Compiler error while compiling XFree86-3.9.17

2000-02-01 Thread Gergely EGERVARY

 I assume this is a compiler bug. Is there a workaround or a patch 
 available for the system compiler or should I install the gcc-devel port
 (for which I probably don't have enough disk space, but oh well)?

yes, it's a bug, and you can work around it by removing the CFLAG -O2

anyway, XFree86 3.9.16 worked fine for me. 3.9.17 eats up all of my CPU
time even if it's idle, so I had to downgrade it to 3.3.6

what is this new int10h code? really want to do real-mode bios calls? hey'
guys, is this what we all want?

OK, it's not an XFree86 discussion forum, please don't reply to this
here :)

-- mauzi



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message