public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/65000] ICE in in expand_builtin_eh_common, at except.c:2072 Date: Tue, 10 Feb 2015 13:12:00 -0000 [thread overview] Message-ID: <bug-65000-4-KFQCTQY8iB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65000-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65000 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to Lars Gullik Bjønnes from comment #0) > I can provide pre-processed source if wanted. Yes, please. >From gcc-bugs-return-476653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 10 13:16:43 2015 Return-Path: <gcc-bugs-return-476653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21501 invoked by alias); 10 Feb 2015 13:16:43 -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 21445 invoked by uid 48); 10 Feb 2015 13:16:40 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64992] More optimize opportunity Date: Tue, 10 Feb 2015 13:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org 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: cc Message-ID: <bug-64992-4-wWBOjRiomS@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64992-4@http.gcc.gnu.org/bugzilla/> References: <bug-64992-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/msg00986.txt.bz2 Content-length: 735 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd992 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Well, b is not volatile. The difference is that 2U * (1 == c) we expand during gimplification as if (1 == c) iftmp = 2; else iftmp = 0; while b * (1 == c) is expanded as multiplication of the EQ_EXPR result and nothing at the tree level changes that afterwards. Perhaps something for match.pd, though not sure if such an transformation is always a win.
next parent reply other threads:[~2015-02-10 13:12 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65000-4@http.gcc.gnu.org/bugzilla/> 2015-02-10 13:12 ` mpolacek at gcc dot gnu.org [this message] 2015-02-10 13:44 ` larsbj at gullik dot net 2015-02-10 13:55 ` trippels at gcc dot gnu.org 2015-02-10 14:05 ` jakub at gcc dot gnu.org 2015-02-10 14:10 ` larsbj at gullik dot net 2015-02-10 14:17 ` mpolacek at gcc dot gnu.org 2015-02-10 16:18 ` jakub at gcc dot gnu.org 2015-02-10 17:53 ` rth at gcc dot gnu.org 2015-02-11 8:45 ` jakub at gcc dot gnu.org 2015-02-11 17:05 ` rth at gcc dot gnu.org 2015-02-11 17:26 ` rth at gcc dot gnu.org 2015-02-12 21:31 ` 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-65000-4-KFQCTQY8iB@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: linkBe 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).