public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56195] New: Error: incorrect register `%rdi' used with `l' suffix (at -O2)
Date: Sun, 03 Feb 2013 16:48:00 -0000	[thread overview]
Message-ID: <bug-56195-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56195
           Summary: Error: incorrect register `%rdi' used with `l' suffix
                    (at -O2)
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: antoine.balestrat@gmail.com


Using GCC 4.8.0 as of 20130203 :

$ xgcc -v
Using built-in specs.
COLLECT_GCC=/home/merkil/gcc/dist/bin/gcc
COLLECT_LTO_WRAPPER=/home/merkil/gcc/dist/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../srcdir/configure CFLAGS='-O2 -pipe' CXXFLAGS='-O2 -pipe'
--enable-languages=c --prefix=/home/merkil/gcc/dist
Thread model: posix
gcc version 4.8.0 20130203 (experimental) (GCC) 

$ cat reg.c
int i, a, t, b, c, d, e, f, j, *h;

void fn(void)
{
    if(b)
    {
        int *p, *q;
        char g;

        if(f++)
            for(;; e++);
lbl:
        for(b = 0; b < 2; b++)
            t /= d + 1 ? : i || a < c < (d = f) ? : 1 | (j = 2);

        *p = g >= *q ^ c != a ^ *p;

        if(!e)
        {
            q = p;
            goto lbl;
        }
    }

    if(h++)
        goto lbl;
}

$ xgcc -O2 reg.c
{standard input}: Assembler messages:
{standard input}:112: Error: incorrect register `%rdi' used with `l' suffix


             reply	other threads:[~2013-02-03 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03 16:48 antoine.balestrat at gmail dot com [this message]
2013-02-03 21:02 ` [Bug tree-optimization/56195] [4.8 Regression] " jakub at gcc dot gnu.org
2013-02-04  9:41 ` rguenth at gcc dot gnu.org
2013-02-05 13:57 ` jakub at gcc dot gnu.org
2013-02-05 16:40 ` jakub at gcc dot gnu.org
2013-02-07 19:25 ` [Bug rtl-optimization/56195] " vmakarov at redhat dot com
2013-02-07 19:47 ` jakub at gcc dot gnu.org
2013-02-07 20:03 ` jakub at gcc dot gnu.org
2013-02-07 20:09 ` vmakarov at redhat dot com
2013-02-08 15:19 ` jakub at gcc dot gnu.org
2013-02-08 15:25 ` jakub at gcc dot gnu.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=bug-56195-4@http.gcc.gnu.org/bugzilla/ \
    --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).