public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: carlo@alinoe.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: other/8919: ICE with (possibly invalid) extended asm.
Date: Fri, 13 Dec 2002 03:24:00 -0000	[thread overview]
Message-ID: <20021213112448.9156.qmail@sources.redhat.com> (raw)

Old Synopsis: Internal Compiler Error with (possibly invalid) extended asm.
New Synopsis: ICE with (possibly invalid) extended asm.

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Fri Dec 13 03:24:47 2002
State-Changed-Why:
    Confirmed.
    
    gcc 2.95.x and 3.0.x issue parse errors.
    The 3.2-branchs issues an ICE.
    Mainline compiles the code.
    (Well, that's not exactly true, since we get assembler errors, but they are
    not related to the problem. There's something wrong with the
              "movl (%[M_bitset_ptr],%[M_digit],4), %[tmp]\n\t"
    lines in the function find1.)
    
    
    A reduced testcase is the following:
    
    ------------------------------snip here----------------------------------
    template <int n> struct A
    {
        int m;
        void foo()
        {
            int i;
            asm ( "testl %[m], %[m]" : [m] "=r" (m), [i] "=r" (i) : );
        }
    };
    
    void bar()
    {
        A<0> a;
        a.foo();
    }
    ------------------------------snip here----------------------------------

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8919


                 reply	other threads:[~2002-12-13 11:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021213112448.9156.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=carlo@alinoe.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).