From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13132 invoked by alias); 13 Nov 2013 05:17:29 -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 13109 invoked by uid 48); 13 Nov 2013 05:17:25 -0000 From: "octoploid at yandex dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59083] -fisolate-erroneous-paths produces illegal instruction with enabled -fprofile-generate Date: Wed, 13 Nov 2013 05:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: octoploid at yandex dot com X-Bugzilla-Status: WAITING 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: Message-ID: In-Reply-To: References: 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-11/txt/msg01183.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59083 --- Comment #9 from Markus Trippelsdorf --- (In reply to Jeffrey A. Law from comment #8) > Should be fixed via recent commits. Specifically, we preserve the *0 for > code that wants to catch the null pointer deref. Well, if you had run the simple glibc testcase that I've posted above, you would have found out that your recent commits don't fix this issue. It's obvious, not only from the amount of churn, that fisolate-erroneous-paths shouldn't be enabled by default at -O2. The very few users you would like SIGSEGV to be transformed to SIGILL by the compiler should set this option explicitly.