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/56999] [4.8/4.9 Regression] LRA caused miscompilation of xulrunner Date: Thu, 18 Apr 2013 16:42:00 -0000 [thread overview] Message-ID: <bug-56999-4-xnyU92xwRL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56999-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56999 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-18 16:42:34 UTC --- BTW, of course much lower priority, this also shows another spot where I think reload code is better. In the same ebb as the wrong-code, reload has code like: movl %eax, %ecx shrb $3, %cl andl $1, %ecx ... movb %cl, 23(%esp) while LRA generates: movl %eax, %ecx shrb $3, %cl movb %cl, 31(%esp) ... andb $1, 31(%esp) I'd think anding the value while we still have it in a register ought to be better, though I admit I haven't benchmarked it.
next prev parent reply other threads:[~2013-04-18 16:42 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-18 16:28 [Bug rtl-optimization/56999] New: " jakub at gcc dot gnu.org 2013-04-18 16:30 ` [Bug rtl-optimization/56999] " jakub at gcc dot gnu.org 2013-04-18 16:42 ` jakub at gcc dot gnu.org [this message] 2013-04-18 17:39 ` jakub at gcc dot gnu.org 2013-04-18 18:28 ` vmakarov at redhat dot com 2013-04-19 5:25 ` [Bug rtl-optimization/56999] [4.8 " jakub at gcc dot gnu.org 2013-04-19 8:19 ` mpolacek at gcc dot gnu.org 2013-04-19 8:19 ` mpolacek at gcc dot gnu.org 2013-04-30 6:57 ` evangelos at foutrelis dot com 2013-05-02 19:31 ` jakub 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-56999-4-xnyU92xwRL@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).