public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Sascha Schumann <sascha@schumann.2ns.de>
To: egcs-bugs@egcs.cygnus.com
Subject: Bug report: internal compiler error
Date: Mon, 31 May 1999 21:06:00 -0000	[thread overview]
Message-ID: <19990524163341.A18405@schumann.2ns.de> (raw)

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

Hello,

we encounter an internal compiler error on multiple platforms (at least
Alpha/Linux and Sparc/Solaris).

This does not happen anymore, if I change a struct member declaration from
unsigned char to unsigned int (it is extended_info in the attached cgi_main.i).

Thank you for your support.

Compiler      egcs-1.1.2 (release)
System        Linux 2.2.9 alpha
Output

gcc -O6 -mcpu=ev56 -v --save-temps   -I. -I. -I./libzend -I./TSRM  -g -Wall -c
cgi_main.c -o cgi_main.o
Reading specs from
/usr/lib/gcc-lib/alphaev56-unknown-linux-gnu/egcs-2.91.66/spe
cs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
 /usr/lib/gcc-lib/alphaev56-unknown-linux-gnu/egcs-2.91.66/cpp -lang-c -v -I.
-I. -I./libzend -I./TSRM -undef -D__GNUC__=2 -D__GNUC_MINOR__=91 -Dlinux
-Dunix -D
_LONGLONG -D__alpha__ -D__ELF__ -D__linux__ -D__unix__ -D_LONGLONG -D__alpha__
-
D__ELF__ -D__linux -D__unix -Asystem(linux) -D__OPTIMIZE__ -g -Wall
-D__LANGUAGE
_C__ -D__LANGUAGE_C -DLANGUAGE_C -Acpu(alpha) -Amachine(alpha) -D__alpha
-D__alp
ha__ -D__alpha_ev5__ -Acpu(ev5) -D__alpha_bwx__ -Acpu(bwx) cgi_main.c
cgi_main.i
GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (Alpha GNU/Linux
for
ELF)
#include "..." search starts here:
#include <...> search starts here:
 .
 libzend
 TSRM
 /usr/local/include
 /usr/alphaev56-unknown-linux-gnu/include
 /usr/lib/gcc-lib/alphaev56-unknown-linux-gnu/egcs-2.91.66/include
/usr/include
End of search list.
 /usr/lib/gcc-lib/alphaev56-unknown-linux-gnu/egcs-2.91.66/cc1 cgi_main.i
-quiet
 -dumpbase cgi_main.c -mcpu=ev56 -g -O6 -Wall -version -o cgi_main.s
GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release)
(alphaev56-unknown-linu
x-gnu) compiled by GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release).
toplev.c:2261: Internal compiler error in function float_signal


-- 

          Regards,

                            Sascha Schumann
                                 Consultant

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

             reply	other threads:[~1999-05-31 21:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-31 21:06 Sascha Schumann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 15:05 BUG report : Internal " R.J.Sivakumar
2001-06-13 19:05 bug report: " Rob Kaper
2000-09-14  1:16 BUG REPORT: Internal Compiler error Thomas Hendel
     [not found] <Pine.HPX.4.21.0004272125500.1168-101000@verdande.diku.dk>
2000-04-27 13:33 ` bug report: Internal compiler error Martin v. Loewis
1999-10-31 23:03 BUG REPORT: internal " Steve Madsen
1999-10-08  4:23 ` Gerald Pfeifer
1999-06-17 11:09 Bug Report: Internal Compiler Error Bill Wendling
1999-06-30 23:07 ` Martin v. Loewis
1998-08-22  1:58 Ramon Fernandez
1998-08-22  8:54 ` Martin von Loewis
1998-07-10  5:31 Bug report: internal compiler error C. van Reeuwijk
1998-07-11  7:27 ` Martin von Loewis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990524163341.A18405@schumann.2ns.de \
    --to=sascha@schumann.2ns.de \
    --cc=egcs-bugs@egcs.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).