> Sending out an attachment of that size to a public mailing list was
> hardly necessary, and the increasing stridency of your posts leading
> up to this only serve to indicate that you may be heading in the truly
> wrong direction with all this and seriously need to rethink your
> strategy before you do something that has people howling for your
> blood.
>
> - Jordan
Okay folks,
This is the scoop.
For the benefit of those which don't have access to the latest XFree86 release you can
download the file from ftp://rah.star-gate.com/pub/bug.c
uname -a
FreeBSD x.star-gate.com 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Mon Dec 27 13:55:25 PST
1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MUADIB i386
gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
gcc -c -O2 bug.c
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 [0xffffffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffffffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffffffd8])) 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))))
------------------------------
Without -O or -O2 the program compiles okay.
gcc -c bug.c
According to Peter, the ports/lang/gcc-devel (the current snapshot) appears to
compile this program fine -- that is the compiler bug has been fixed.
So there appears to be two solutions to get around this problem:
1. compile without -O
or
2. installed the latest snapshot of gcc.
Take Care Guys
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
