public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/37262] Two branches of the same condition being emitted Date: Sat, 30 Aug 2008 01:43:00 -0000 [thread overview] Message-ID: <20080830014145.1375.qmail@sourceware.org> (raw) In-Reply-To: <bug-37262-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-30 01:41 ------- I have seen this in other cases even for the non doloop case, though I don't know if it is because of -O1 or because it is not removing it. Testcase: int _bfd_xcoff_canonicalize_dynamic_reloc (unsigned long long l_symndx) { if (l_symndx < 3) { switch (l_symndx) { case 0: case 1: break; case 2: return _bfd_abort (); } } } --- CUT --- Compile at -O1 on powerpc-linux and you will see the double branches: bne 0,.L7 bne 0,.L8 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262
next prev parent reply other threads:[~2008-08-30 1:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-28 2:03 [Bug rtl-optimization/37262] New: " pinskia at gcc dot gnu dot org 2008-08-29 4:39 ` [Bug rtl-optimization/37262] " pinskia at gcc dot gnu dot org 2008-08-30 1:43 ` pinskia at gcc dot gnu dot org [this message] 2010-03-02 18:29 ` pinskia at gcc dot gnu dot 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=20080830014145.1375.qmail@sourceware.org \ --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).