public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65032] [5 Regression] ICE in reload_combine_note_use, at postreload.c:1556 on i686-linux-gnu
Date: Sun, 22 Feb 2015 19:39:00 -0000	[thread overview]
Message-ID: <bug-65032-4-FZhVJnV7jV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65032-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65032

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |trippels at gcc dot gnu.org

--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
I cannot reproduce the original issue.

For the testcase from comment 2:

markus@x4 tmp % g++ -c -w -m32 -Os -std=gnu++11 -fPIC -fstack-protector-strong
-fno-strict-aliasing -fno-exceptions  -fomit-frame-pointer testc.ii

In file included from
/builddir/build/BUILD/firefox-36.0/mozilla-release/objdir/dom/media/ogg/Unified_cpp_dom_media_ogg0.cpp:20:0:
/builddir/build/BUILD/firefox-36.0/mozilla-release/dom/media/ogg/OggReader.cpp:
In member function ‘nsresult mozilla::OggReader::DecodeVorbis(ogg_packet*)’:
/builddir/build/BUILD/firefox-36.0/mozilla-release/dom/media/ogg/OggReader.cpp:562:1:
internal compiler error: in reload_combine_note_use, at postreload.c:1556
0xbf4b3a reload_combine_note_use
        ../../gcc/gcc/postreload.c:1556
0xbf48bf reload_combine_note_use
        ../../gcc/gcc/postreload.c:1643
0xbf65f3 reload_combine
        ../../gcc/gcc/postreload.c:1423
0xbf76e0 reload_cse_regs
        ../../gcc/gcc/postreload.c:95
0xbf76e0 execute
        ../../gcc/gcc/postreload.c:2367
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions

Reducing...
>From gcc-bugs-return-478113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 22 18:30:58 2015
Return-Path: <gcc-bugs-return-478113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28318 invoked by alias); 22 Feb 2015 18:30:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28054 invoked by uid 48); 22 Feb 2015 18:30:54 -0000
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65168] New: diagnostic: missing: reference cannot be bound to dereferenced null pointer
Date: Sun, 22 Feb 2015 19:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jan.kratochvil at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cf_gcctarget
Message-ID: <bug-65168-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg02445.txt.bz2
Content-length: 964

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide168

            Bug ID: 65168
           Summary: diagnostic: missing: reference cannot be bound to
                    dereferenced null pointer
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jan.kratochvil at redhat dot com
            Target: x86_64-linux-gnu

int main() {
  int *p=static_cast<int *>(0),&r=*p;
  return !&r;
}

-Wall

g++ (GCC) 5.0.0 20150221 (experimental)
<nothing>

clang++ (clang-3.5.0-6.fc21.x86_64):
ref.C:3:12: warning: reference cannot be bound to dereferenced null pointer in
well-defined C++ code; pointer may be assumed to always convert to true
[-Wundefined-bool-conversion]

I have no idea if it can be miscompiled by either compiler.  Still I find
useful to be notified I write non-conforming C++ code.


  parent reply	other threads:[~2015-02-22 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  4:23 [Bug target/65032] New: " doko at gcc dot gnu.org
2015-02-12 13:12 ` [Bug target/65032] " jakub at gcc dot gnu.org
2015-02-12 13:28 ` rguenth at gcc dot gnu.org
2015-02-22 18:41 ` pbrobinson at gmail dot com
2015-02-22 19:39 ` trippels at gcc dot gnu.org [this message]
2015-02-22 20:53 ` trippels at gcc dot gnu.org
2015-02-25  8:46 ` law at redhat dot com
2015-02-27 15:10 ` vmakarov at gcc dot gnu.org
2015-02-27 15:14 ` trippels 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-65032-4-FZhVJnV7jV@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).