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 target/67573] [SH] wrong code generated for libstdc++-v3/src/c++11/cxx11-shim_facets.cc at -mlra Date: Tue, 15 Sep 2015 23:14:00 -0000 [thread overview] Message-ID: <bug-67573-4-ftnFrVsxdb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67573 --- Comment #4 from Oleg Endo <olegendo at gcc dot gnu.org> --- Maybe FPSCR_STAT_REG should be in the clobber list, too? Otherwise stores of FP exception bits etc (get_fpscr builtin) could be wrongly CSE'd across function calls... However, I don't know if this is a problem at the moment.
next prev parent reply other threads:[~2015-09-15 23:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-14 13:00 [Bug target/67573] New: " kkojima at gcc dot gnu.org 2015-09-14 13:09 ` [Bug target/67573] " kkojima at gcc dot gnu.org 2015-09-15 11:28 ` kkojima at gcc dot gnu.org 2015-09-15 14:13 ` kkojima at gcc dot gnu.org 2015-09-15 23:14 ` olegendo at gcc dot gnu.org [this message] 2015-09-17 0:13 ` kkojima at gcc dot gnu.org 2015-09-17 0:24 ` kkojima at gcc dot gnu.org 2015-09-17 14:28 ` olegendo at gcc dot gnu.org 2015-09-19 12:52 ` kkojima at gcc dot gnu.org 2015-09-20 23:54 ` kkojima 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-67573-4-ftnFrVsxdb@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).