From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26158 invoked by alias); 30 Oct 2013 03:25:33 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26106 invoked by uid 48); 30 Oct 2013 03:25:28 -0000 From: "jason at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/58920] New: Overeager optimization based on TREE_THIS_NOTRAP Date: Wed, 30 Oct 2013 03:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jason at gcc dot gnu.org 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 keywords bug_severity priority component assigned_to reporter attachments.created Message-ID: 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: 2013-10/txt/msg02105.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58920 Bug ID: 58920 Summary: Overeager optimization based on TREE_THIS_NOTRAP Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jason at gcc dot gnu.org Created attachment 31108 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31108&action=edit Patch to set TREE_THIS_NOTRAP for C++ references The TREE_THIS_NOTRAP macro came up in email the other day, and it seemed to me that it would be useful to set on C++ references, since they are required to refer to objects; trying to read from a null reference gives undefined behavior. So I tried the attached patch. But it breaks all the ext_pointer tests in libstdc++. Basically, what's happening is that there is a code path which is never taken which leads to an explicit null dereference. The optimizers see this happening within a loop and decide to hoist it out of the loop. So now it is executed before the loop starts, and causes a SEGV. Is this an appropriate optimization?