public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53805] combine_comparisons changes trapping behavior Date: Fri, 06 Jul 2012 21:53:00 -0000 [thread overview] Message-ID: <bug-53805-4-nkrR1aKSEl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53805-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53805 --- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> 2012-07-06 21:53:32 UTC --- Suspicious code: combine_comparisons has special code that depends on which comparison comes first, but maybe_fold_and_comparisons calls and_comparisons_1 (and thus combine_comparisons) with arguments in both orders. I guess this would give a wrong optimization for ORDERED_EXPR && LT_EXPR, but I am having a hard time creating an ORDERED_EXPR. It looks like invert_tree_comparison shouldn't return ERROR_MARK for (UN)ORDERED_EXPR.
next prev parent reply other threads:[~2012-07-06 21:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-29 11:00 [Bug tree-optimization/53805] New: " glisse at gcc dot gnu.org 2012-06-29 12:02 ` [Bug tree-optimization/53805] " rguenth at gcc dot gnu.org 2012-06-29 12:19 ` glisse at gcc dot gnu.org 2012-06-29 12:22 ` rguenth at gcc dot gnu.org 2012-06-29 14:24 ` joseph at codesourcery dot com 2012-06-29 14:34 ` rguenth at gcc dot gnu.org 2012-06-29 14:43 ` joseph at codesourcery dot com 2012-06-29 14:54 ` rguenth at gcc dot gnu.org 2012-07-02 7:27 ` jakub at gcc dot gnu.org 2012-07-06 21:53 ` glisse at gcc dot gnu.org [this message] 2012-08-02 19:55 ` glisse 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-53805-4-nkrR1aKSEl@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).