public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: alireza@morphotech.com
To: gcc-gnats@gcc.gnu.org
Subject: c/4685: Generating "Compiler Internal Error"
Date: Thu, 25 Oct 2001 16:28:00 -0000	[thread overview]
Message-ID: <20011025173505.17342.qmail@sourceware.cygnus.com> (raw)

>Number:         4685
>Category:       c
>Synopsis:       Generating "Compiler Internal Error"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 25 16:26:26 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Alireza Moshtaghi
>Release:        unknown-1.0
>Organization:
>Environment:
Redhat Linux, Solaris, Cygwin
>Description:
The compiler crashes instead of reporting an error for the case when an array name is passed to an asm block with "+r" constraint. 
The following is the snapshot is produced when compiling with -save-temp  and -v flags:

Reading specs from /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/bin/../lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/specs
gcc version 2.96-gnupro-00r1
 /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/bin/../lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/cpp0.exe -lang-c -v -iprefix /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/bin/../lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/ -D__GNUC__=2 -D__GNUC_MINOR__=96 -D__GNUC_PATCHLEVEL__=0 -D_WIN32 -DWINNT -D_X86_=1 -D_WIN32 -D__WINNT__ -D_X86_=1 -D__WINNT -Asystem(winnt) -remap -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__tune_pentiumpro__ -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_stdcall=__attribute__((__stdcall__)) -D_cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__CYGWIN32__ -D__CYGWIN__ asmtest5.c asmtest5.i
GNU CPP version 2.96-gnupro-00r1 (cpplib) (80386, BSD syntax)
ignoring nonexistent directory "/usr/cygnus/gnupro-00r1/include"
ignoring nonexistent directory "/usr/cygnus/gnupro-00r1/H-i686-pc-cygwin/lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/include"
ignoring nonexistent directory "/usr/cygnus/gnupro-00r1/H-i686-pc-cygwin/i686-pc-cygwin/include"
ignoring nonexistent directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
 /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/include
 /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/i686-pc-cygwin/include
End of search list.
 /cygdrive/c/redhat/gnupro-00r1/H-i686-pc-cygwin/bin/../lib/gcc-lib/i686-pc-cygwin/2.96-gnupro-00r1/cc1.exe asmtest5.i -quiet -dumpbase asmtest5.c -version -o asmtest5.s
GNU C version 2.96-gnupro-00r1 (i686-pc-cygwin) compiled by GNU C version 2.96-gnupro-00r1.
asmtest5.c: In function `main':
asmtest5.c:8: Internal compiler error in `emit_move_insn', at expr.c:2570
Please submit a full bug report.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
>How-To-Repeat:
just compile the attached file:
> gcc asmtest5.c
>Fix:
read the comment inside  the code
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-10-25 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 16:28 alireza [this message]
2001-10-29 20:27 rodrigc

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=20011025173505.17342.qmail@sourceware.cygnus.com \
    --to=alireza@morphotech.com \
    --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: 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).