Re: trouble building XFree86-4-Server under yesterday's current
On Tue, 24 Sep 2002 17:22:36 +0300
Vallo Kallaste <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 24, 2002 at 09:47:44AM -0400, Wesley Morgan
> <[EMAIL PROTECTED]> wrote:
>
> > I have built XFree86 at least 3 times in the past week, all with
> > varying levels of optimization, from -O to -O3 and ALWAYS with
> > -march=pentium3. All of the builds succeeded, although I had
> > stability problems with -O2 and above. Are you _certain_ this is a
> > compiler bug?
>
> To put myself to the safe side, no. I'll do yet another run of
> compilation on all of the CPUTYPE=p[234] levels and report how it
> did tomorrow.
No need. The bug is there and it is triggered by -march={athlon|p[234]}.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Tue, Sep 24, 2002 at 09:47:44AM -0400, Wesley Morgan <[EMAIL PROTECTED]> wrote: > I have built XFree86 at least 3 times in the past week, all with varying > levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3. > All of the builds succeeded, although I had stability problems with -O2 > and above. Are you _certain_ this is a compiler bug? To put myself to the safe side, no. I'll do yet another run of compilation on all of the CPUTYPE=p[234] levels and report how it did tomorrow. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
I have built XFree86 at least 3 times in the past week, all with varying levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3. All of the builds succeeded, although I had stability problems with -O2 and above. Are you _certain_ this is a compiler bug? On Tue, 24 Sep 2002, Vallo Kallaste wrote: > On Mon, Sep 23, 2002 at 03:13:15PM -0700, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > On Mon, Sep 23, 2002 at 01:55:18PM +0300, Vallo Kallaste wrote: > > > > > This isn't a yesterdays problem, I've had this for a month or so. > > > The problem is explicit declaration of -march=p[234], use > > > CPUTYPE=i686 in /etc/make.conf and you get further. The second way > > > is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will > > > set -mcpu to what appears to fit. > > > > That's not true; it adds -mcpu=pentiumpro by default to optimize > > instruction scheduling for 686-class CPUs (without breaking binary > > compatibility down to i386s), but it doesnt "autodetect" anything, and > > you'll get better performance on a 686-class CPU by specifying it in > > CPUTYPE (since you'll then also get pentium pro instructions). > > > > -mcpu != -march > > Yes I know and it was what I meant to say. By setting CPUTYPE=p[234] > excplicitly in /etc/make.conf you'll get the build failure in > XFree86-4-Server because bsd.cpu.mk will set excplicit -march, not > -mcpu. But the build error happens _only_ if one sets CPUTYPE=p[234] > and not in case CPUTYPE=i686, the latter sets -march=pentiumpro, not > -march=pentium[234]. Hope this is all clear now and sorry about > confusion, english isn't my native tongue after all. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, Sep 23, 2002 at 03:13:15PM -0700, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Mon, Sep 23, 2002 at 01:55:18PM +0300, Vallo Kallaste wrote: > > > This isn't a yesterdays problem, I've had this for a month or so. > > The problem is explicit declaration of -march=p[234], use > > CPUTYPE=i686 in /etc/make.conf and you get further. The second way > > is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will > > set -mcpu to what appears to fit. > > That's not true; it adds -mcpu=pentiumpro by default to optimize > instruction scheduling for 686-class CPUs (without breaking binary > compatibility down to i386s), but it doesnt "autodetect" anything, and > you'll get better performance on a 686-class CPU by specifying it in > CPUTYPE (since you'll then also get pentium pro instructions). > > -mcpu != -march Yes I know and it was what I meant to say. By setting CPUTYPE=p[234] excplicitly in /etc/make.conf you'll get the build failure in XFree86-4-Server because bsd.cpu.mk will set excplicit -march, not -mcpu. But the build error happens _only_ if one sets CPUTYPE=p[234] and not in case CPUTYPE=i686, the latter sets -march=pentiumpro, not -march=pentium[234]. Hope this is all clear now and sorry about confusion, english isn't my native tongue after all. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, Sep 23, 2002 at 01:55:18PM +0300, Vallo Kallaste wrote: > This isn't a yesterdays problem, I've had this for a month or so. > The problem is explicit declaration of -march=p[234], use > CPUTYPE=i686 in /etc/make.conf and you get further. The second way > is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will > set -mcpu to what appears to fit. That's not true; it adds -mcpu=pentiumpro by default to optimize instruction scheduling for 686-class CPUs (without breaking binary compatibility down to i386s), but it doesnt "autodetect" anything, and you'll get better performance on a 686-class CPU by specifying it in CPUTYPE (since you'll then also get pentium pro instructions). -mcpu != -march Kris msg43280/pgp0.pgp Description: PGP signature
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, Sep 23, 2002 at 11:08:13AM -0400, Alexander Kabaev <[EMAIL PROTECTED]> wrote: > > Heh, this sounds like a joke.. because I have written at least three > > messages to -current list about the very same thing. I know that > > following -current list for day-to-day basis is challenge, but > > nevertheless this surprises me. Seems like nobody has read my > > messages nor find the cause of this failure interesting. Yes this > > caused bu machine type optimisation and everybody who's brave enough > > to set CPUTYPE=p[234] will be trapped. > > You might want to report the bug to GCC developers first instead of > sending your complaints here. Some help finding the offending function > and providing people with additional information will come a long way > toward having this bug finally fixed. Please consult > http://gcc.gnu.org/bugs.html for instructions if you decide to do so. I'm not complaining, only reporting what I found. It's quite unfair for non-developer to complain about development track, IMHO. I'll see what I can do, but finding offending function is probably beyond my knowledge. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, 23 Sep 2002 17:54:25 +0300 Vallo Kallaste <[EMAIL PROTECTED]> wrote: > Heh, this sounds like a joke.. because I have written at least three > messages to -current list about the very same thing. I know that > following -current list for day-to-day basis is challenge, but > nevertheless this surprises me. Seems like nobody has read my > messages nor find the cause of this failure interesting. Yes this > caused bu machine type optimisation and everybody who's brave enough > to set CPUTYPE=p[234] will be trapped. You might want to report the bug to GCC developers first instead of sending your complaints here. Some help finding the offending function and providing people with additional information will come a long way toward having this bug finally fixed. Please consult http://gcc.gnu.org/bugs.html for instructions if you decide to do so. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, Sep 23, 2002 at 04:31:38PM +0300, Giorgos Keramidas <[EMAIL PROTECTED]> wrote: [snip] > > This isn't a yesterdays problem, I've had this for a month or so. > > The problem is explicit declaration of -march=p[234], use > > CPUTYPE=i686 in /etc/make.conf and you get further. The second way > > is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will > > set -mcpu to what appears to fit. > > If you suspect the machine type optimizations for problems like this, > you might want to try adding the following to /etc/make.conf too: > > NO_CPU_CFLAGS= true# Don't add -march= to CFLAGS automatically > NO_CPU_COPTFLAGS=true # Don't add -march= to COPTFLAGS automatically Heh, this sounds like a joke.. because I have written at least three messages to -current list about the very same thing. I know that following -current list for day-to-day basis is challenge, but nevertheless this surprises me. Seems like nobody has read my messages nor find the cause of this failure interesting. Yes this caused bu machine type optimisation and everybody who's brave enough to set CPUTYPE=p[234] will be trapped. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On 2002-09-23 13:55, Vallo Kallaste wrote:
> On Mon, Sep 23, 2002 at 03:08:02AM -0700, "David P. Reese Jr." <[EMAIL PROTECTED]>
>wrote:
> > Current as of yesterday
> >
> > The XFree86 server build dies with an odd compiler message. I have no clue
> > what it means.
> >
> > [snip]
> > LD_LIBRARY_PATH=/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/lib cc -O
>-pipe -march=pentium2 -march=pentium2 -ansi -pedantic -Dasm=__asm -Wall
>-Wpointer-arith -fno-merge-constants -I. -I../include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include/X11
>-I../../../include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include
>-I/usr/X11R6/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP
>-DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER
>-DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension
>-DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE
>-DBUILDDEBUG -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO
>-DIN_MODULE -DXFree86Module-c miPck1Prim.c
> > miPck1Prim.c: In function `CheckFAreaPick1':
> > miPck1Prim.c:337: unable to find a register to spill in class `FLOAT_REGS'
> > miPck1Prim.c:337: this is the insn:
> > (insn 275 273 277 (set (subreg:SF (reg/v:DI 29 rmm0 [64]) 0)
> > (float:SF (mem/s/j:HI (reg/v/f:SI 2 ecx [61]) [0 .x+0 S2 A16])))
>167 {floathisf2} (insn_list 271 (nil))
> > (nil))
> > miPck1Prim.c:337: confused by earlier errors, bailing out
> > *** Error code 1
> >
> > Stop in
>/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level1.
> > *** Error code 1
>
> This isn't a yesterdays problem, I've had this for a month or so.
> The problem is explicit declaration of -march=p[234], use
> CPUTYPE=i686 in /etc/make.conf and you get further. The second way
> is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will
> set -mcpu to what appears to fit.
If you suspect the machine type optimizations for problems like this,
you might want to try adding the following to /etc/make.conf too:
NO_CPU_CFLAGS= true# Don't add -march= to CFLAGS automatically
NO_CPU_COPTFLAGS=true # Don't add -march= to COPTFLAGS automatically
Giorgos.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Mon, Sep 23, 2002 at 03:08:02AM -0700, "David P. Reese Jr." <[EMAIL PROTECTED]>
wrote:
> Current as of yesterday
>
> [daver@metropolis:/usr/ports/sysutils/xmbmon]$ uname -a
> FreeBSD metropolis.gomerbud.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sun Sep 22
>10:42:53 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/METROPOLIS
>i386
>
> The XFree86 server build dies with an odd compiler message. I have no clue
> what it means.
>
> [snip]
> LD_LIBRARY_PATH=/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/lib cc -O
>-pipe -march=pentium2 -march=pentium2 -ansi -pedantic -Dasm=__asm -Wall
>-Wpointer-arith -fno-merge-constants -I. -I../include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include/X11
>-I../../../include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc
>-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include
>-I/usr/X11R6/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP
>-DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER
>-DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension
>-DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE
>-DBUILDDEBUG -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO
>-DIN_MODULE -DXFree86Module-c miPck1Prim.c
> miPck1Prim.c: In function `CheckFAreaPick1':
> miPck1Prim.c:337: unable to find a register to spill in class `FLOAT_REGS'
> miPck1Prim.c:337: this is the insn:
> (insn 275 273 277 (set (subreg:SF (reg/v:DI 29 rmm0 [64]) 0)
> (float:SF (mem/s/j:HI (reg/v/f:SI 2 ecx [61]) [0 .x+0 S2 A16])))
>167 {floathisf2} (insn_list 271 (nil))
> (nil))
> miPck1Prim.c:337: confused by earlier errors, bailing out
> *** Error code 1
>
> Stop in
>/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level1.
> *** Error code 1
This isn't a yesterdays problem, I've had this for a month or so.
The problem is explicit declaration of -march=p[234], use
CPUTYPE=i686 in /etc/make.conf and you get further. The second way
is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will
set -mcpu to what appears to fit.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
trouble building XFree86-4-Server under yesterday's current
Current as of yesterday
[daver@metropolis:/usr/ports/sysutils/xmbmon]$ uname -a
FreeBSD metropolis.gomerbud.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sun Sep 22
10:42:53 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/METROPOLIS
i386
The XFree86 server build dies with an odd compiler message. I have no clue
what it means.
[snip]
LD_LIBRARY_PATH=/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/lib cc -O
-pipe -march=pentium2 -march=pentium2 -ansi -pedantic -Dasm=__asm -Wall
-Wpointer-arith -fno-merge-constants -I. -I../include
-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include/X11
-I../../../include
-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include
-I/usr/ports/x11-servers/XFree86-4-Server/work/xc
-I/usr/ports/x11-servers/XFree86-4-Server/work/xc/exports/include
-I/usr/X11R6/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP
-DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPANORAMIX -DRENDER
-DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension
-DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE
-DBUILDDEBUG -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO
-DIN_MODULE -DXFree86Module-c miPck1Prim.c
miPck1Prim.c: In function `CheckFAreaPick1':
miPck1Prim.c:337: unable to find a register to spill in class `FLOAT_REGS'
miPck1Prim.c:337: this is the insn:
(insn 275 273 277 (set (subreg:SF (reg/v:DI 29 rmm0 [64]) 0)
(float:SF (mem/s/j:HI (reg/v/f:SI 2 ecx [61]) [0 .x+0 S2 A16]))) 167
{floathisf2} (insn_list 271 (nil))
(nil))
miPck1Prim.c:337: confused by earlier errors, bailing out
*** Error code 1
Stop in
/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level1.
*** Error code 1
Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5.
*** Error code 1
Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver.
*** Error code 1
Stop in /usr/ports/x11-servers/XFree86-4-Server.
[daver@metropolis:/usr/ports/x11-servers/XFree86-4-Server]$
--
David P. Reese Jr. [EMAIL PROTECTED]
--
C
You shoot yourself in the foot.
Assembler
You try to shoot yourself in the foot, only to discover you must first
invent the gun, the bullet, the trigger, and your foot.
How to Shoot Yourself in the Foot
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
