public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46771] New: [4.6 Regression] -fcompare-debug failure (length) with -O -ftree-vectorize
Date: Thu, 02 Dec 2010 21:22:00 -0000	[thread overview]
Message-ID: <bug-46771-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.6 Regression] -fcompare-debug failure (length) with
                    -O -ftree-vectorize
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
                CC: aoliva@gcc.gnu.org
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


Created attachment 22607
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22607
reduced testcase

Output:
$ gcc -O -ftree-vectorize -fcompare-debug pr46771.c             
gcc: error: pr46771.c: -fcompare-debug failure (length)
$ diff pr46771.*gkd
11c11
...(long output)
There's a difference in generated code with(out) -g.

Tested revisions:
r167383 - fail
r165699 - fail
r161659 - OK
4.5 r166509 - OK


             reply	other threads:[~2010-12-02 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 21:22 zsojka at seznam dot cz [this message]
2010-12-02 22:59 ` [Bug debug/46771] " hjl.tools at gmail dot com
2010-12-06  8:06 ` jakub at gcc dot gnu.org
2010-12-06 19:30 ` jakub at gcc dot gnu.org
2010-12-06 19:39 ` 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-46771-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).