public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56365] Missed opportunities for smin/smax standard name patterns when compiling as C++ Date: Thu, 31 Jul 2014 17:04:00 -0000 [thread overview] Message-ID: <bug-56365-4-hYAU8QZCrw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56365-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56365 --- Comment #4 from Oleg Endo <olegendo at gcc dot gnu.org> --- As of r213381 this problem still exists. compiled as C 003t.original: ;; Function min (null) ;; enabled by -tree-original { return MIN_EXPR <b, a>; } ;; Function max (null) ;; enabled by -tree-original { return MAX_EXPR <a, b>; } ;; Function test_04 (null) ;; enabled by -tree-original { return max (-128, min (127, a)); } compiled as C++ 003t.original: ;; Function int min(int, int) (null) ;; enabled by -tree-original return <retval> = a < b ? a : b; ;; Function int max(int, int) (null) ;; enabled by -tree-original return <retval> = a < b ? b : a; ;; Function int test_04(int, int) (null) ;; enabled by -tree-original <<cleanup_point return <retval> = max (-128, min (127, a))>>;
next prev parent reply other threads:[~2014-07-31 17:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-17 15:27 [Bug tree-optimization/56365] New: Missed opportunities for smin/smax standard name patterns olegendo at gcc dot gnu.org 2013-02-18 10:58 ` [Bug tree-optimization/56365] " rguenth at gcc dot gnu.org 2013-02-18 20:05 ` olegendo at gcc dot gnu.org 2014-05-10 12:52 ` [Bug tree-optimization/56365] Missed opportunities for smin/smax standard name patterns when compiling as C++ olegendo at gcc dot gnu.org 2014-07-31 17:04 ` olegendo at gcc dot gnu.org [this message] 2014-10-17 10:14 ` olegendo at gcc dot gnu.org 2014-10-17 11:41 ` rguenth 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-56365-4-hYAU8QZCrw@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).