public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/50489] [UPC/IA64] mis-schedule of MEM ref with -ftree-vectorize and -fschedule-insns2 Date: Fri, 23 Sep 2011 10:11:00 -0000 [thread overview] Message-ID: <bug-50489-4-mJoiXNHux8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50489-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50489 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> 2011-09-23 09:30:01 UTC --- Does the problem vanish if you add -fno-strict-aliasing? One more thing, you mention -O2 in the flags, but then refer to selective scheduler, which is only enabled at -O3. Perhaps you meant Haifa scheduler.
next prev parent reply other threads:[~2011-09-23 9:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-22 19:22 [Bug rtl-optimization/50489] New: " gary at intrepid dot com 2011-09-22 19:30 ` [Bug rtl-optimization/50489] " gary at intrepid dot com 2011-09-22 19:33 ` gary at intrepid dot com 2011-09-23 10:11 ` amonakov at gcc dot gnu.org [this message] 2011-09-23 17:59 ` gary at intrepid dot com 2011-09-25 12:26 ` rguenth at gcc dot gnu.org 2011-09-25 20:06 ` gary at intrepid dot com 2011-10-17 3:04 ` gary at intrepid dot com 2012-08-20 20:54 ` olegendo at gcc dot gnu.org 2024-03-28 4:31 ` pinskia 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-50489-4-mJoiXNHux8@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).