Re: bug in snapshot 19990629

Re: bug in snapshot 19990629

[Alexandre Oliva]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

On Jul  3, 1999, Berthold Höllmann <bhoel@server.python.net> wrote:

> xport.c:172: fixed or forbidden register 2 (cx) was spilled for class CREG.

http://egcs.cygnus.com/faq.html#asmclobber

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
{oliva,Alexandre.Oliva}@dcc.unicamp.br  aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists

Re: bug in snapshot 19990629

[Berthold Höllmann]

craig@jcb-sc.com wrote:
> 
> >I think I've come over a Bug in egcs snapshot 19990629 while trying to
> [...]
> >This error seems to be fixed in 19990629.
> 
> I'm confused.  Is the bug fixed in 19990629, or present in it?
> 
> Also, I don't read MIME attachments, unless there's absolutely no
> alternative.  Please use plaintext for bug reports, patches, etc.,
> whenever possible.  (I think we only recently updated our web site
> to make this request more explicit.)
> 
>         tq vm, (burley)

The problem fixed was the one I had with g77:


g77 -c -O6 -mpentiumpro -march=pentiumpro -fPIC -fno-globals -Wall
-Wno-globals  buasds.f
../../../gcc/f/com.c:1905: failed assertion `ix != FFECOM_gfrt'
g77: Internal compiler error: program f771 got fatal signal 6

Somewhere beween 1.1.2 and 19990629 the problem I had with gcc was
introduced, but, according to the anwer from Alexandre Oliva it is a
Linux, not a gcc (egcs) problem.

Thanks

Berthold
-- 
bhoel@starship.python.net / http://starship.python.net/crew/bhoel/
        It is unlawful to use this email address for unsolicited ads
        (USC Title 47 Sec.227). I will assess a US$500 charge for
        reviewing and deleting each unsolicited ad.
>From law@cygnus.com Wed Jul 07 01:13:00 1999
From: Jeffrey A Law <law@cygnus.com>
To: David Coder <dacoder@max.dcoder.com>
Cc: egcs-bugs@egcs.cygnus.com
Subject: Re: Internal compiler error in compiling egcs-2.95 
Date: Wed, 07 Jul 1999 01:13:00 -0000
Message-id: <15074.931335081@upchuck.cygnus.com>
References: <37813A5E.EF93B325@max.dcoder.com>
X-SW-Source: 1999-07/msg00237.html
Content-length: 1278

  In message < 37813A5E.EF93B325@max.dcoder.com >you write:
  > In trying to compile egcs-2.95 on a PentiumPro running SCO Unixware7 I
  > encountered the following error:
  > 
  >        true libio.a
  >         test x"no" != xyes || \
  >           /home/src/egcs-2.9.5/gcc/xgcc -B/home/src/egcs-2.9.5/gcc/
  > -B/usr/local/i686-UnixWare7.0.1-sysv5/bin/ -c -g -O2
  > -fno-implicit-templates -I. -I. -nostdinc++   builtinbuf.cc -o
  > pic/builtinbuf.o
  >         /home/src/egcs-2.9.5/gcc/xgcc -B/home/src/egcs-2.9.5/gcc/
  > -B/usr/local/i686-UnixWare7.0.1-sysv5/bin/ -c -g -O2
  > -fno-implicit-templates -I. -I. -nostdinc++  builtinbuf.cc
  >         test x"no" != xyes || \
  >           /home/src/egcs-2.9.5/gcc/xgcc -B/home/src/egcs-2.9.5/gcc/
  > -B/usr/local/i686-UnixWare7.0.1-sysv5/bin/ -c -g -O2
  > -fno-implicit-templates -I. -I. -nostdinc++   filebuf.cc -o
  > pic/filebuf.o
  >         /home/src/egcs-2.9.5/gcc/xgcc -B/home/src/egcs-2.9.5/gcc/
  > -B/usr/local/i686-UnixWare7.0.1-sysv5/bin/ -c -g -O2
  > -fno-implicit-templates -I. -I. -nostdinc++  filebuf.cc
  > filebuf.cc:215: Internal compiler error in `modified_type_die', at
  > dwarf2out.c:6473
  > 
  > The only option that I passed  to make was 'bootstrap'.
I believe this should be fixed now.
jeff

Re: bug in snapshot 19990629

[craig]

>The f77 frontend error was in 1.1.2 and is gone away in the current
>snapshot. 

Ah, okay, good!

>Typically the CPP output will be large, so please compress the
>resulting file with one of the popular compression programs such as
>gzip, bzip2, compress or pkzip, then include the compressed CPP output
>as an attachment to your message.
>
>Is this no more true? what is requested for a bug report nowerdays?

I think the term "attachment" is the problem there.  I don't believe
the authors intended that in the MIME sense.  Even if so, I believe
we've recently changed the request.  Check the latest web pages
at < http://egcs.cygnus.com/ >.

In any case, I'm pretty sure most readers of this list have no problem
with MIME attachments.  There are just a few of us that do, some of
us being almost the only ones who can work on certain types of bugs (e.g.
those involving the g77 front end).

So your use of a MIME attachment for a C-related bug might not be a
problem at all.

        tq vm, (burley)
>From dvv@dvv.ru Thu Jul 08 07:28:00 1999
From: dvv@dvv.ru (Dima Volodin)
To: "Krueger, Mark S" <mskrueger@switch.com>
Cc: "'egcs-bugs@egcs.cygnus.com'" <egcs-bugs@egcs.cygnus.com>
Subject: Re: webpage problem
Date: Thu, 08 Jul 1999 07:28:00 -0000
Message-id: <3786b570.46195915@localhost>
References: <617829F216CED011966000805F59E0730297567B@exchptc1.switch.com>
X-SW-Source: 1999-07/msg00296.html
Content-length: 575

Reboot your Windows.


Dima

On Thu, 08 Jul 1999 10:12:43 -0400, you wrote:

>Hi.  There's a problem with your webpage:
>	http://egcs.cygnus.com/onlinedocs/gcc_2.html
>
>With both Netscape 4.51 and MS-IE4, text on this page for the last 1/4 of
>the page or so is unreadable and has strikethrough marks over it.  
>
>- Mark
>
>__________________________________________________
>Mark Krueger,   A&IS Infrastructures, 1 West Riverside
>Union Switch & Signal
>1000 Technology Drive, Pittsburgh, PA  15219, USA
>(412) 688-2234, fax 688-2399, Mailto:mskrueger@switch.com
>
>
>
>

Re: bug in snapshot 19990629

[Alexandre Oliva]

On Jul  8, 1999, craig@jcb-sc.com wrote:

>> gzip, bzip2, compress or pkzip, then include the compressed CPP output
>> as an attachment to your message.

> I think the term "attachment" is the problem there.  I don't believe
> the authors intended that in the MIME sense.

I'm not 100% I was the one who wrote that passage, but MIME is
certainly the best option to send compressed data nowadays.  The
alternative is uuencode, which is not as handy, neither for the bug
reporter nor for me.

-- 
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

Re: bug in snapshot 19990629

[Berthold Höllmann]

craig@jcb-sc.com wrote:
> 
> >I think I've come over a Bug in egcs snapshot 19990629 while trying to
> [...]
> >This error seems to be fixed in 19990629.
> 
> I'm confused.  Is the bug fixed in 19990629, or present in it?

Sorry, I didn't want to confuse you. 

The attachements are related to something I thougth was a bug in the C
frontend of egcs, but seems to be a Linux bug according to the answer I
got from Alexandre Oliva. 

The f77 frontend error was in 1.1.2 and is gone away in the current
snapshot. 

> 
> Also, I don't read MIME attachments, unless there's absolutely no
> alternative.  Please use plaintext for bug reports, patches, etc.,
> whenever possible.  (I think we only recently updated our web site
> to make this request more explicit.)

I had an extract from an older egcs FAQ related to egcs bug reports
local on my hardisc, where I read:

-- snip --
In short, if egcs says Internal compiler error (or any other error
that you'd like us to be able to reproduce, for that matter), please
mail a bug report to egcs-bugs@cygnus.com including:

    The egcs version 
    The system type 
    All options you passed to egcs 
    Preprocessed output of the source file that caused the compiler
    error
-- snip --

and later:

-- snip --
Typically the CPP output will be large, so please compress the
resulting file with one of the popular compression programs such as
gzip, bzip2, compress or pkzip, then include the compressed CPP output
as an attachment to your message.
-- snip --

Is this no more true? what is requested for a bug report nowerdays?

> 
>         tq vm, (burley)


Greetings

Berthold
-- 
bhoel@starship.python.net / http://starship.python.net/crew/bhoel/
        It is unlawful to use this email address for unsolicited ads
        (USC Title 47 Sec.227). I will assess a US$500 charge for
        reviewing and deleting each unsolicited ad.

Re: bug in snapshot 19990629

[craig]

>I think I've come over a Bug in egcs snapshot 19990629 while trying to
[...]
>This error seems to be fixed in 19990629.

I'm confused.  Is the bug fixed in 19990629, or present in it?

Also, I don't read MIME attachments, unless there's absolutely no
alternative.  Please use plaintext for bug reports, patches, etc.,
whenever possible.  (I think we only recently updated our web site
to make this request more explicit.)

        tq vm, (burley)

bug in snapshot 19990629

[Berthold Höllmann]

[-- Attachment #1: Type: text/plain, Size: 2723 bytes --]

Sorry when this comes out double, but I made this report on tuesday to
egcs-bugs@cygnus.com. When looked at the egcs bugs mailing list archive
today I couldn't find it, so I think it got lost somewhere.


Hello,

I think I've come over a Bug in egcs snapshot 19990629 while trying to
compile xgks-2.5.5. Compilation completed when I used egcs 1.1.2. I used
the snapshot, because I had problems with 1.1.2 g77 on some files. I
got:

g77 -c -O6 -mpentiumpro -march=pentiumpro -fPIC -fno-globals -Wall
-Wno-globals  buasds.f
../../../gcc/f/com.c:1905: failed assertion `ix != FFECOM_gfrt'
g77: Internal compiler error: program f771 got fatal signal 6

This error seems to be fixed in 19990629.

Attached is the output of

>env PATH=/usr/local/bin:$PATH gcc -v --save-temps -O -c -I.. -I../../../port -I/usr/include -DNDEBUG -O6 -mpentiumpro -march=pentiumpro xport.c
Reading specs from
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/specs
gcc version gcc-2.95 19990629 (prerelease)
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/cpp -lang-c -v -I..
-I../../../port -I/usr/include -D__GNUC__=2 -D__GNUC_MINOR__=95
-D__ELF__ -Dunix -D__i386__ -Dlinux -D__ELF__ -D__unix__ -D__i386__
-D__linux__ -D__unix -D__linux -Asystem(posix) -D__OPTIMIZE__
-Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di686
-Dpentiumpro -D__i686 -D__i686__ -D__pentiumpro -D__pentiumpro__
-DNDEBUG xport.c xport.i
GNU CPP version gcc-2.95 19990629 (prerelease) (i386 Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
 ..
 ../../../port
 /usr/include
 /usr/local/pgsql/include
 /usr/local/include

/usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/../../../../i686-pc-linux-gnu/include
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/include
 /usr/include
End of search list.
The following default directories have been omitted from the search
path:
 

/usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/../../../../include/g++-2
End of omitted list.
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/gcc-2.95/cc1 xport.i
-mcpu=pentiumpro -quiet -dumpbase xport.c -mpentiumpro -march=pentiumpro
-O -O6 -version -o xport.s
GNU C version gcc-2.95 19990629 (prerelease) (i686-pc-linux-gnu)
compiled by GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release).
xport.c: In function `XgksAwaitEvent':
xport.c:172: Invalid `asm' statement:
xport.c:172: fixed or forbidden register 2 (cx) was spilled for class
CREG.

Greetings

Berthold
-- 
bhoel@starship.python.net / http://starship.python.net/crew/bhoel/
        It is unlawful to use this email address for unsolicited ads
        (USC Title 47 Sec.227). I will assess a US$500 charge for
        reviewing and deleting each unsolicited ad.
xport.i.bz2
xport.s.bz2


[-- Attachment #2: xport.i.bz2 --]
[-- Type: application/x-bzip2, Size: 22684 bytes --]

[-- Attachment #3: xport.s.bz2 --]
[-- Type: application/x-bzip2, Size: 608 bytes --]