public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ishiura-compiler at ml dot kwansei.ac.jp" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64992] More optimize opportunity Date: Sun, 15 Feb 2015 23:32:00 -0000 [thread overview] Message-ID: <bug-64992-4-110ytN6Tgv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64992-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64992 --- Comment #4 from Ishiura Lab Compiler Team <ishiura-compiler at ml dot kwansei.ac.jp> --- FYI, clang-3.6 -O3 seems to do the same optimization on "org.c" as well as on "opt.c."
next prev parent reply other threads:[~2015-02-15 23:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-10 3:01 [Bug tree-optimization/64992] New: " ishiura-compiler at ml dot kwansei.ac.jp 2015-02-10 10:18 ` [Bug tree-optimization/64992] " rguenth at gcc dot gnu.org 2015-02-15 5:15 ` ishiura-compiler at ml dot kwansei.ac.jp 2015-02-15 23:32 ` ishiura-compiler at ml dot kwansei.ac.jp [this message] 2021-11-29 3:51 ` pinskia at gcc dot gnu.org 2021-11-30 22:08 ` pinskia at gcc dot gnu.org 2021-11-30 22:18 ` pinskia at gcc dot gnu.org 2021-12-01 5:53 ` pinskia at gcc dot gnu.org 2022-08-15 16:41 ` cvs-commit at gcc dot gnu.org 2022-09-10 21:10 ` roger at nextmovesoftware dot com
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-64992-4-110ytN6Tgv@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).