public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46716] [4.4/4.5/4.6/4.7 Regression] wrong code generated with -mno-sse2 -m64 Date: Fri, 02 Mar 2012 14:36:00 -0000 [thread overview] Message-ID: <bug-46716-4-PZm5hpsOpl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46716-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46716 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.4/4.5/4.6/4.7/4.8 |[4.4/4.5/4.6/4.7 |Regression] wrong code |Regression] wrong code |generated with -mno-sse2 |generated with -mno-sse2 |-m64 |-m64 --- Comment #8 from Uros Bizjak <ubizjak at gmail dot com> 2012-03-02 14:35:24 UTC --- This is just a matter of always forcing the "natural" mode for the register, even when type system does not agree with this. See the comment for gen_reg_or_parallel on this issue. I am testing following patch: Index: config/i386/i386.c =================================================================== --- config/i386/i386.c (revision 184774) +++ config/i386/i386.c (working copy) @@ -6338,15 +6338,16 @@ construct_container (enum machine_mode mode, enum } if (n == 2 && regclass[0] == X86_64_SSE_CLASS && regclass[1] == X86_64_SSEUP_CLASS && mode != BLKmode) - return gen_rtx_REG (mode, SSE_REGNO (sse_regno)); + return gen_reg_or_parallel (mode, orig_mode, + SSE_REGNO (sse_regno)); if (n == 4 && regclass[0] == X86_64_SSE_CLASS && regclass[1] == X86_64_SSEUP_CLASS && regclass[2] == X86_64_SSEUP_CLASS && regclass[3] == X86_64_SSEUP_CLASS && mode != BLKmode) - return gen_rtx_REG (mode, SSE_REGNO (sse_regno)); - + return gen_reg_or_parallel (mode, orig_mode, + SSE_REGNO (sse_regno)); if (n == 2 && regclass[0] == X86_64_X87_CLASS && regclass[1] == X86_64_X87UP_CLASS) return gen_rtx_REG (XFmode, FIRST_STACK_REG);
next prev parent reply other threads:[~2012-03-02 14:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-30 0:59 [Bug c/46716] New: bad " mathog at caltech dot edu 2010-11-30 10:01 ` [Bug target/46716] [4.3/4.4/4.5/4.6 Regression] " jakub at gcc dot gnu.org 2010-11-30 12:36 ` rguenth at gcc dot gnu.org 2010-11-30 12:59 ` jakub at gcc dot gnu.org 2010-11-30 13:49 ` hjl.tools at gmail dot com 2010-11-30 17:50 ` mathog at caltech dot edu 2010-12-05 12:03 ` rguenth at gcc dot gnu.org 2011-01-03 20:28 ` rguenth at gcc dot gnu.org 2011-06-27 13:40 ` [Bug target/46716] [4.3/4.4/4.5/4.6/4.7 Regression] wrong " rguenth at gcc dot gnu.org 2012-03-02 14:36 ` ubizjak at gmail dot com [this message] 2012-03-02 17:04 ` [Bug target/46716] [4.4/4.5/4.6/4.7/4.8 " uros at gcc dot gnu.org 2012-03-13 14:08 ` [Bug target/46716] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-07-02 12:10 ` rguenth at gcc dot gnu.org 2013-04-12 15:16 ` [Bug target/46716] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-01-23 7:12 ` law at redhat 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-46716-4-PZm5hpsOpl@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).