public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
@ 1999-08-01 16:22 Alexander L. Belikoff
  1999-08-01 16:56 ` Jeffrey A Law
  1999-08-31 23:20 ` Alexander L. Belikoff
  0 siblings, 2 replies; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-01 16:22 UTC (permalink / raw)
  To: egcs

Yep - justs failed to build on:

- Alpha dp264 (dual CPU)
- RedHat 5.2
- egcs 1.1.2, binutils 2.9.1.0.15-1

This is pretty painful and surprising, considering that egcs-19990712
built just fine. Anybody cares to fix that or just "stick to RedHat
6.0, you pathetic looser!" ;-)

We are slowly migrating on our Alphas from RedHat 4.2 to RedHat 5.2.
6.0 is out of question - there are too many complaints about general
stability and speed. On RedHat 5.2 the situation with the compilers is
the following:

1. Egcs 1.0.3 (supplied by RedHat) - gives ICE on certain optimization
   flags (I reported it quite a while ago).

2. Egcs 1.1.2 (built manually) - has the infamous memcpy bug.

3. Gcc 2.95 - fails to build.

This doesn't look very optimistic, does it? ;-) Anyway, here goes the
make log:


if [ x"no" = xyes ]; then \
  /bb/home/abel/eb/gcc/xgcc -B/bb/home/abel/eb/gcc/ -B/usr/local/gcc-2.95/alphaev6-unknown-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates  -mieee -I../../../../gcc-2.95/libstdc++ -I../../../../gcc-2.95/libstdc++/stl -I../libio -I../../../../gcc-2.95/libstdc++/../libio -nostdinc++ -D_IO_MTSAFE_IO  -DF \
    `for N in MAIN ADDCC ADDCF ADDFC SUBCC SUBCF SUBFC MULCC MULCF MULFC DIVCC DIVCF DIVFC PLUS MINUS EQCC EQCF EQFC NECC NECF NEFC ABS ARG POLAR CONJ NORM COS COSH EXP LOG POWCC POWCF POWCI POWFC SIN SINH SQRT; do echo " -D${N}"; done` \
    ../../../../gcc-2.95/libstdc++/cinst.cc -o pic/fcomplex.o; \
else true ; fi
/bb/home/abel/eb/gcc/xgcc -B/bb/home/abel/eb/gcc/ -B/usr/local/gcc-2.95/alphaev6-unknown-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates  -mieee -I../../../../gcc-2.95/libstdc++ -I../../../../gcc-2.95/libstdc++/stl -I../libio -I../../../../gcc-2.95/libstdc++/../libio -nostdinc++ -D_IO_MTSAFE_IO -DF `for N in MAIN ADDCC ADDCF ADDFC SUBCC SUBCF SUBFC MULCC MULCF MULFC DIVCC DIVCF DIVFC PLUS MINUS EQCC EQCF EQFC NECC NECF NEFC ABS ARG POLAR CONJ NORM COS COSH EXP LOG POWCC POWCF POWCI POWFC SIN SINH SQRT; do echo " -D${N}"; done` \
  ../../../../gcc-2.95/libstdc++/cinst.cc -o fcomplex.o
/tmp/cc2jzCeM.s: Assembler messages:
/tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
/tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
make[4]: *** [bigstmp-complx] Error 1
make[4]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/ieee/libstdc++'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/libstdc++'
make[2]: *** [multi-all] Error 2
make[2]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/libstdc++'
make[1]: *** [all-target-libstdc++] Error 2
make[1]: Leaving directory `/bb/home/abel/eb'
make: *** [bootstrap] Error 2


PS. In case you are going to suggest upgrading binutils, could you
please also explain what exactly was fine with the latter package 3
weeks ago, that got horribly wrong now?..

Thanks in advance,


-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 16:22 gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2 Alexander L. Belikoff
@ 1999-08-01 16:56 ` Jeffrey A Law
  1999-08-01 17:21   ` Alexander L. Belikoff
  1999-08-31 23:20   ` Jeffrey A Law
  1999-08-31 23:20 ` Alexander L. Belikoff
  1 sibling, 2 replies; 14+ messages in thread
From: Jeffrey A Law @ 1999-08-01 16:56 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

  In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
  > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
  > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
Your assembler is out of date.  Get a newer one.

jeff

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 16:56 ` Jeffrey A Law
@ 1999-08-01 17:21   ` Alexander L. Belikoff
  1999-08-01 17:35     ` Jeffrey A Law
                       ` (2 more replies)
  1999-08-31 23:20   ` Jeffrey A Law
  1 sibling, 3 replies; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-01 17:21 UTC (permalink / raw)
  To: egcs

Jeffrey A Law <law@cygnus.com> writes:

>   In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
>   > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
>   > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
> Your assembler is out of date.  Get a newer one.
> 
> jeff

But it was good enough three weeks ago, when gcc was in (apparent)
deep freeze! Is there any reason for losing backward compatibility in
such an abrupt way? Binutils is a major package we are definitely not
going to upgrade it unless such an upgrade is critical - we are
talking about production systems... This basically rules out
*previous* (read, "stable") release of a major Linux distribution...
:-(

-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 17:21   ` Alexander L. Belikoff
@ 1999-08-01 17:35     ` Jeffrey A Law
  1999-08-31 23:20       ` Jeffrey A Law
  1999-08-02 19:07     ` Alexandre Oliva
  1999-08-31 23:20     ` Alexander L. Belikoff
  2 siblings, 1 reply; 14+ messages in thread
From: Jeffrey A Law @ 1999-08-01 17:35 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

  In message < m3wvvf9ptb.fsf@vermis.bfr.co.il >you write:
  > But it was good enough three weeks ago, when gcc was in (apparent)
  > deep freeze! Is there any reason for losing backward compatibility in
  > such an abrupt way? Binutils is a major package we are definitely not
  > going to upgrade it unless such an upgrade is critical - we are
  > talking about production systems... This basically rules out
  > *previous* (read, "stable") release of a major Linux distribution...
The assembler is broken, plain and simple.  Get a newer one.  There may be
a way to disable those instructions, but I wouldn't know what it is since
I do not normally work on alphas,

jeff

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 17:21   ` Alexander L. Belikoff
  1999-08-01 17:35     ` Jeffrey A Law
@ 1999-08-02 19:07     ` Alexandre Oliva
  1999-08-02 23:42       ` Richard Henderson
                         ` (2 more replies)
  1999-08-31 23:20     ` Alexander L. Belikoff
  2 siblings, 3 replies; 14+ messages in thread
From: Alexandre Oliva @ 1999-08-02 19:07 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

On Aug  1, 1999, abel@bfr.co.il (Alexander L. Belikoff) wrote:

> Jeffrey A Law <law@cygnus.com> writes:
>> In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
>> > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
>> > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'

>> Your assembler is out of date.  Get a newer one.

> But it was good enough three weeks ago, when gcc was in (apparent)
> deep freeze!

Was it on the very same host (i.e., was config.guess' output the
same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
(this is just intended as an example)

I could build gcc 2.95 on a RedHat 6.0/alpha (an AlphaStation 200),
with binutils 2.9.1.0.24 (the one that ships with RH6.0), if this
helps.

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-02 19:07     ` Alexandre Oliva
@ 1999-08-02 23:42       ` Richard Henderson
  1999-08-31 23:20         ` Richard Henderson
  1999-08-03  5:07       ` Alexander L. Belikoff
  1999-08-31 23:20       ` Alexandre Oliva
  2 siblings, 1 reply; 14+ messages in thread
From: Richard Henderson @ 1999-08-02 23:42 UTC (permalink / raw)
  To: Alexandre Oliva; +Cc: Alexander L. Belikoff, egcs

On Mon, Aug 02, 1999 at 11:07:18PM -0300, Alexandre Oliva wrote:
> Was it on the very same host (i.e., was config.guess' output the
> same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
> (this is just intended as an example)

The sqrt insn appears as of ev6.


r~

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-02 19:07     ` Alexandre Oliva
  1999-08-02 23:42       ` Richard Henderson
@ 1999-08-03  5:07       ` Alexander L. Belikoff
  1999-08-31 23:20         ` Alexander L. Belikoff
  1999-08-31 23:20       ` Alexandre Oliva
  2 siblings, 1 reply; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-03  5:07 UTC (permalink / raw)
  To: egcs

Alexandre Oliva <oliva@dcc.unicamp.br> writes:

> On Aug  1, 1999, abel@bfr.co.il (Alexander L. Belikoff) wrote:
> 
> > Jeffrey A Law <law@cygnus.com> writes:
> >> In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
> >> > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
> >> > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
> 
> >> Your assembler is out of date.  Get a newer one.
> 
> > But it was good enough three weeks ago, when gcc was in (apparent)
> > deep freeze!
> 
> Was it on the very same host (i.e., was config.guess' output the
> same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
> (this is just intended as an example)

/usr/local/egcs.new/bin/gcc -v
Reading specs from /usr/local/egcs.new/lib/gcc-lib/alphaev6-unknown-linux-gnu/2.95/specs
gcc version 2.95 19990712 (prerelease)

-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 17:21   ` Alexander L. Belikoff
  1999-08-01 17:35     ` Jeffrey A Law
  1999-08-02 19:07     ` Alexandre Oliva
@ 1999-08-31 23:20     ` Alexander L. Belikoff
  2 siblings, 0 replies; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-31 23:20 UTC (permalink / raw)
  To: egcs

Jeffrey A Law <law@cygnus.com> writes:

>   In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
>   > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
>   > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
> Your assembler is out of date.  Get a newer one.
> 
> jeff

But it was good enough three weeks ago, when gcc was in (apparent)
deep freeze! Is there any reason for losing backward compatibility in
such an abrupt way? Binutils is a major package we are definitely not
going to upgrade it unless such an upgrade is critical - we are
talking about production systems... This basically rules out
*previous* (read, "stable") release of a major Linux distribution...
:-(

-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-03  5:07       ` Alexander L. Belikoff
@ 1999-08-31 23:20         ` Alexander L. Belikoff
  0 siblings, 0 replies; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-31 23:20 UTC (permalink / raw)
  To: egcs

Alexandre Oliva <oliva@dcc.unicamp.br> writes:

> On Aug  1, 1999, abel@bfr.co.il (Alexander L. Belikoff) wrote:
> 
> > Jeffrey A Law <law@cygnus.com> writes:
> >> In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
> >> > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
> >> > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
> 
> >> Your assembler is out of date.  Get a newer one.
> 
> > But it was good enough three weeks ago, when gcc was in (apparent)
> > deep freeze!
> 
> Was it on the very same host (i.e., was config.guess' output the
> same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
> (this is just intended as an example)

/usr/local/egcs.new/bin/gcc -v
Reading specs from /usr/local/egcs.new/lib/gcc-lib/alphaev6-unknown-linux-gnu/2.95/specs
gcc version 2.95 19990712 (prerelease)

-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 16:56 ` Jeffrey A Law
  1999-08-01 17:21   ` Alexander L. Belikoff
@ 1999-08-31 23:20   ` Jeffrey A Law
  1 sibling, 0 replies; 14+ messages in thread
From: Jeffrey A Law @ 1999-08-31 23:20 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

  In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
  > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
  > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
Your assembler is out of date.  Get a newer one.

jeff

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-02 19:07     ` Alexandre Oliva
  1999-08-02 23:42       ` Richard Henderson
  1999-08-03  5:07       ` Alexander L. Belikoff
@ 1999-08-31 23:20       ` Alexandre Oliva
  2 siblings, 0 replies; 14+ messages in thread
From: Alexandre Oliva @ 1999-08-31 23:20 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

On Aug  1, 1999, abel@bfr.co.il (Alexander L. Belikoff) wrote:

> Jeffrey A Law <law@cygnus.com> writes:
>> In message < m33dy3b73j.fsf@vermis.bfr.co.il >you write:
>> > /tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
>> > /tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'

>> Your assembler is out of date.  Get a newer one.

> But it was good enough three weeks ago, when gcc was in (apparent)
> deep freeze!

Was it on the very same host (i.e., was config.guess' output the
same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
(this is just intended as an example)

I could build gcc 2.95 on a RedHat 6.0/alpha (an AlphaStation 200),
with binutils 2.9.1.0.24 (the one that ships with RH6.0), if this
helps.

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 17:35     ` Jeffrey A Law
@ 1999-08-31 23:20       ` Jeffrey A Law
  0 siblings, 0 replies; 14+ messages in thread
From: Jeffrey A Law @ 1999-08-31 23:20 UTC (permalink / raw)
  To: Alexander L. Belikoff; +Cc: egcs

  In message < m3wvvf9ptb.fsf@vermis.bfr.co.il >you write:
  > But it was good enough three weeks ago, when gcc was in (apparent)
  > deep freeze! Is there any reason for losing backward compatibility in
  > such an abrupt way? Binutils is a major package we are definitely not
  > going to upgrade it unless such an upgrade is critical - we are
  > talking about production systems... This basically rules out
  > *previous* (read, "stable") release of a major Linux distribution...
The assembler is broken, plain and simple.  Get a newer one.  There may be
a way to disable those instructions, but I wouldn't know what it is since
I do not normally work on alphas,

jeff

^ permalink raw reply	[flat|nested] 14+ messages in thread

* gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-01 16:22 gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2 Alexander L. Belikoff
  1999-08-01 16:56 ` Jeffrey A Law
@ 1999-08-31 23:20 ` Alexander L. Belikoff
  1 sibling, 0 replies; 14+ messages in thread
From: Alexander L. Belikoff @ 1999-08-31 23:20 UTC (permalink / raw)
  To: egcs

Yep - justs failed to build on:

- Alpha dp264 (dual CPU)
- RedHat 5.2
- egcs 1.1.2, binutils 2.9.1.0.15-1

This is pretty painful and surprising, considering that egcs-19990712
built just fine. Anybody cares to fix that or just "stick to RedHat
6.0, you pathetic looser!" ;-)

We are slowly migrating on our Alphas from RedHat 4.2 to RedHat 5.2.
6.0 is out of question - there are too many complaints about general
stability and speed. On RedHat 5.2 the situation with the compilers is
the following:

1. Egcs 1.0.3 (supplied by RedHat) - gives ICE on certain optimization
   flags (I reported it quite a while ago).

2. Egcs 1.1.2 (built manually) - has the infamous memcpy bug.

3. Gcc 2.95 - fails to build.

This doesn't look very optimistic, does it? ;-) Anyway, here goes the
make log:


if [ x"no" = xyes ]; then \
  /bb/home/abel/eb/gcc/xgcc -B/bb/home/abel/eb/gcc/ -B/usr/local/gcc-2.95/alphaev6-unknown-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates  -mieee -I../../../../gcc-2.95/libstdc++ -I../../../../gcc-2.95/libstdc++/stl -I../libio -I../../../../gcc-2.95/libstdc++/../libio -nostdinc++ -D_IO_MTSAFE_IO  -DF \
    `for N in MAIN ADDCC ADDCF ADDFC SUBCC SUBCF SUBFC MULCC MULCF MULFC DIVCC DIVCF DIVFC PLUS MINUS EQCC EQCF EQFC NECC NECF NEFC ABS ARG POLAR CONJ NORM COS COSH EXP LOG POWCC POWCF POWCI POWFC SIN SINH SQRT; do echo " -D${N}"; done` \
    ../../../../gcc-2.95/libstdc++/cinst.cc -o pic/fcomplex.o; \
else true ; fi
/bb/home/abel/eb/gcc/xgcc -B/bb/home/abel/eb/gcc/ -B/usr/local/gcc-2.95/alphaev6-unknown-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates  -mieee -I../../../../gcc-2.95/libstdc++ -I../../../../gcc-2.95/libstdc++/stl -I../libio -I../../../../gcc-2.95/libstdc++/../libio -nostdinc++ -D_IO_MTSAFE_IO -DF `for N in MAIN ADDCC ADDCF ADDFC SUBCC SUBCF SUBFC MULCC MULCF MULFC DIVCC DIVCF DIVFC PLUS MINUS EQCC EQCF EQFC NECC NECF NEFC ABS ARG POLAR CONJ NORM COS COSH EXP LOG POWCC POWCF POWCI POWFC SIN SINH SQRT; do echo " -D${N}"; done` \
  ../../../../gcc-2.95/libstdc++/cinst.cc -o fcomplex.o
/tmp/cc2jzCeM.s: Assembler messages:
/tmp/cc2jzCeM.s:3711: Error: unknown opcode `sqrttsu'
/tmp/cc2jzCeM.s:3781: Error: unknown opcode `sqrttsu'
make[4]: *** [bigstmp-complx] Error 1
make[4]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/ieee/libstdc++'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/libstdc++'
make[2]: *** [multi-all] Error 2
make[2]: Leaving directory `/bb/home/abel/eb/alphaev6-unknown-linux-gnu/libstdc++'
make[1]: *** [all-target-libstdc++] Error 2
make[1]: Leaving directory `/bb/home/abel/eb'
make: *** [bootstrap] Error 2


PS. In case you are going to suggest upgrading binutils, could you
please also explain what exactly was fine with the latter package 3
weeks ago, that got horribly wrong now?..

Thanks in advance,


-- 
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@vallinor4.com, abel@bfr.co.il

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2
  1999-08-02 23:42       ` Richard Henderson
@ 1999-08-31 23:20         ` Richard Henderson
  0 siblings, 0 replies; 14+ messages in thread
From: Richard Henderson @ 1999-08-31 23:20 UTC (permalink / raw)
  To: Alexandre Oliva; +Cc: Alexander L. Belikoff, egcs

On Mon, Aug 02, 1999 at 11:07:18PM -0300, Alexandre Oliva wrote:
> Was it on the very same host (i.e., was config.guess' output the
> same)?  Maybe you get this opcode for alphaev56, but not for alphaev5
> (this is just intended as an example)

The sqrt insn appears as of ev6.


r~

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~1999-08-31 23:20 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-08-01 16:22 gcc-2.95 build FAILED! - RedHat Linux/Alpha 5.2 Alexander L. Belikoff
1999-08-01 16:56 ` Jeffrey A Law
1999-08-01 17:21   ` Alexander L. Belikoff
1999-08-01 17:35     ` Jeffrey A Law
1999-08-31 23:20       ` Jeffrey A Law
1999-08-02 19:07     ` Alexandre Oliva
1999-08-02 23:42       ` Richard Henderson
1999-08-31 23:20         ` Richard Henderson
1999-08-03  5:07       ` Alexander L. Belikoff
1999-08-31 23:20         ` Alexander L. Belikoff
1999-08-31 23:20       ` Alexandre Oliva
1999-08-31 23:20     ` Alexander L. Belikoff
1999-08-31 23:20   ` Jeffrey A Law
1999-08-31 23:20 ` Alexander L. Belikoff

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).