public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101701] GCC optimization and code generation for if-else chains vs ternary chains vs a switch Date: Fri, 30 Jul 2021 23:39:39 +0000 [thread overview] Message-ID: <bug-101701-4-N1Dz9lEEaw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101701-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101701 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- int foo(int val) { if (val == 1) return val; else if(val == 2) return val; else if(val == 3) return val; else if(val == 4) return val; else return -1; } int bar(int val) { return val == 1 ? val : (val == 2 ? val : (val == 3 ? val : (val == 4 ? val : -1))); } int baz(int val) { switch(val) { case 1: case 2: case 3: case 4: return val; default: return -1; } }
next prev parent reply other threads:[~2021-07-30 23:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-30 23:37 [Bug c++/101701] New: " llvm at rifkin dot dev 2021-07-30 23:39 ` pinskia at gcc dot gnu.org [this message] 2021-07-30 23:48 ` [Bug tree-optimization/101701] " pinskia at gcc dot gnu.org 2021-07-30 23:50 ` pinskia at gcc dot gnu.org 2021-07-30 23:53 ` llvm at rifkin dot dev 2021-08-03 9:25 ` marxin 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-101701-4-N1Dz9lEEaw@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).