public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex dot neyman at auriga dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18160] New: ICE on taking register variable address
Date: Tue, 26 Oct 2004 13:17:00 -0000	[thread overview]
Message-ID: <20041026131740.18160.alex.neyman@auriga.ru> (raw)

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

I know this is invalid, but: 
- it produces a warning, not an error; 
- reliable compilers never crash, do they? 
 
Testcase: 
-------------------------- 
void f(void) 
{ 
        register int x asm("eax"); 
        g(&x); 
} 
-------------------------- 
objdir/gcc/xgcc -Bobjdir/gcc -c f.c 
f.c: In function ‘f’: 
f.c:5: warning: address of register variable ‘x’ requested 
f.c:5: warning: address of register variable ‘x’ requested 
f.c:5: internal compiler error: in expand_expr_addr_expr_1, at expr.c:5975 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
 
Sources checked out as of today morning (about 6 hours ago).

-- 
           Summary: ICE on taking register variable address
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: alex dot neyman at auriga dot ru
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18160


             reply	other threads:[~2004-10-26 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 13:17 alex dot neyman at auriga dot ru [this message]
2004-10-26 13:20 ` [Bug c/18160] " alex dot neyman at auriga dot ru
2004-10-26 13:22 ` [Bug middle-end/18160] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-10-26 21:24 ` nemet at gcc dot gnu dot org
2004-10-28 15:16 ` steven at gcc dot gnu dot org
2004-10-28 19:30 ` cvs-commit at gcc dot gnu dot org
2004-10-28 19:31 ` cvs-commit at gcc dot gnu dot org
2004-10-28 19:32 ` nemet at gcc dot gnu dot org
2004-11-10 21:11 ` cvs-commit at gcc dot gnu dot org
2004-11-10 21:11 ` cvs-commit at gcc dot gnu dot org

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=20041026131740.18160.alex.neyman@auriga.ru \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).