public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57003] [4.8/4.9 Regression] gcc-4.8.0 breaks -O2 optimization with Wine(64) - links/info/bisect of commits included Date: Thu, 25 Apr 2013 09:54:00 -0000 [thread overview] Message-ID: <bug-57003-4-njLrYBTtAt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57003-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57003 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-25 09:54:20 UTC --- Created attachment 29936 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29936 gcc49-pr57003.patch Untested fix. While we kill_clobbered_value early, for SET in CALL_INSN_FUNCTION_USAGE we add a value equivalence. In standard x86_64 ABI %rdi is invalidated by the call and present in the hard reg set to invalidate, so it is removed again, and perhaps if there is some target where the first argument is passed in non-call-clobbered register, the equivalence is correct. So, what the patch does is in this case apply the clobbers again. Bernd, does this look reasonable to you as the author of those changes?
next prev parent reply other threads:[~2013-04-25 9:54 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-19 0:46 [Bug c/57003] New: " triplesquarednine at gmail dot com 2013-04-19 0:55 ` [Bug middle-end/57003] " pinskia at gcc dot gnu.org 2013-04-19 1:00 ` pinskia at gcc dot gnu.org 2013-04-19 8:26 ` rguenth at gcc dot gnu.org 2013-04-21 14:22 ` dank at kegel dot com 2013-04-21 18:06 ` pinskia at gcc dot gnu.org 2013-04-22 16:39 ` dank at kegel dot com 2013-04-23 9:44 ` kirill.k.smirnov at math dot spbu.ru 2013-04-23 9:51 ` jakub at gcc dot gnu.org 2013-04-23 15:57 ` kirill.k.smirnov at math dot spbu.ru 2013-04-23 16:00 ` jakub at gcc dot gnu.org 2013-04-23 21:33 ` kirill.k.smirnov at math dot spbu.ru 2013-04-23 22:01 ` kirill.k.smirnov at math dot spbu.ru 2013-04-24 9:25 ` bernds at gcc dot gnu.org 2013-04-24 16:06 ` kirill.k.smirnov at math dot spbu.ru 2013-04-24 16:50 ` [Bug rtl-optimization/57003] [4.8/4.9 Regression] " jakub at gcc dot gnu.org 2013-04-24 18:24 ` jakub at gcc dot gnu.org 2013-04-24 18:45 ` jakub at gcc dot gnu.org 2013-04-25 7:51 ` jakub at gcc dot gnu.org 2013-04-25 9:54 ` jakub at gcc dot gnu.org [this message] 2013-04-25 10:12 ` bernds at gcc dot gnu.org 2013-04-26 17:50 ` kirill.k.smirnov at math dot spbu.ru 2014-10-03 14:24 ` [Bug rtl-optimization/57003] [4.8/4.9/5.0 Regression] gcc " ubizjak at gmail dot com 2014-10-03 17:55 ` ubizjak at gmail dot com 2014-10-03 18:08 ` jakub at gcc dot gnu.org 2014-10-03 18:10 ` ubizjak at gmail dot com 2014-10-09 6:36 ` uros at gcc dot gnu.org 2014-10-09 8:22 ` uros at gcc dot gnu.org 2014-10-09 9:06 ` uros 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-57003-4-njLrYBTtAt@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).