public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: redstone@cs.washington.edu To: gcc-gnats@gcc.gnu.org Subject: c/3344: internal compiler error in 'change_address', at emit-rtl.c on alpha Date: Thu, 21 Jun 2001 11:46:00 -0000 [thread overview] Message-ID: <20010621183646.22932.qmail@sourceware.cygnus.com> (raw) >Number: 3344 >Category: c >Synopsis: internal compiler error in 'change_address', at emit-rtl.c on alpha >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 21 11:46:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Joshua Redstone >Release: 2.95.3 20010315 (release) >Organization: >Environment: main% uname -a OSF1 venus.cs.washington.edu V4.0 1229 alpha main% /projects/smt11/redstone/usr/local/bin/gcc -v Reading specs from /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/specs gcc version 2.95.3 20010315 (release) >Description: On an alpha running Tru64 4.0f, when compiling c-parse.c from application 126.gcc of SPECInt95 with the flag -ffixed-\$15, I get interenal compiler error. Other flags, such as -ffixed-\$14 don't induce the error. Similarly, other c files compile OK with the -ffixed-\$5 flag. Here is the command line that produces the error: main% /projects/smt11/redstone/usr/local/bin/gcc -v -save-temps -c -o c-parse.o -DSPEC -O3 -mcpu=ev6 -ffixed-\$15 c-parse.c Reading specs from /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/specs gcc version 2.95.3 20010315 (release) /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/cpp0 -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=95 -Dunix -D__osf__ -D_LONGLONG -DSYSTYPE_BSD -D_SYSTYPE_BSD -D__unix__ -D__osf__ -D_LONGLONG -D__SYSTYPE_BSD__ -D_SYSTYPE_BSD -D__unix -D__SYSTYPE_BSD -Asystem(unix) -Asystem(xpg4) -D__OPTIMIZE__ -D__LANGUAGE_C__ -D__LANGUAGE_C -DLANGUAGE_C -Acpu(alpha) -Amachine(alpha) -D__alpha -D__alpha__ -D__alpha_ev6__ -Acpu(ev6) -D__alpha_bwx__ -Acpu(bwx) -D__alpha_max__ -Acpu(max) -D__alpha_fix__ -Acpu(fix) -DSPEC c-parse.c c-parse.i GNU CPP version 2.95.3 20010315 (release) #include "..." search starts here: #include <...> search starts here: /usr/local/include /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/../../../../alphaev6-dec-osf4.0f/include /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/include /usr/include End of search list. The following default directories have been omitted from the search path: /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/../../../../include/g++-3 End of omitted list. /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/cc1 c-parse.i -quiet -dumpbase c-parse.c -mcpu=ev6 -O3 -version -ffixed-$15 -o c-parse.s GNU C version 2.95.3 20010315 (release) (alphaev6-dec-osf4.0f) compiled by GNU C version 2.95.3 20010315 (release). In file included from /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/include/stdarg.h:36, from gvarargs.h:4, from tree.h:20, from c-parse.y:50: /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/include/va-alpha.h:36: warning: redefinition of `va_list' /projects/smt11/redstone/usr/local/lib/gcc-lib/alphaev6-dec-osf4.0f/2.95.3/include/va_list.h:7: warning: `va_list' previously declared here bison.simple: In function `yyparse': bison.simple:315: warning: type mismatch in implicit declaration for built-in function `alloca' bison.simple:674: Internal compiler error in `change_address', at emit-rtl.c:1619 Please submit a full bug report. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. >How-To-Repeat: Compile the file as I described. The file is located in /spec/benchspec/CINT95/126.gcc/src of the SPECInt95 distribution. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-21 11:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-21 11:46 redstone [this message] 2002-04-24 14:35 rth
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=20010621183646.22932.qmail@sourceware.cygnus.com \ --to=redstone@cs.washington.edu \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).