public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10077: gcc -msse2 generates movd to move dwords between xmm regs Date: Fri, 14 Mar 2003 09:36:00 -0000 [thread overview] Message-ID: <20030314093601.32274.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10077; it has been noted by GNATS. From: Andreas Jaeger <aj@suse.de> To: douze@enseeiht.fr Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/10077: gcc -msse2 generates movd to move dwords between xmm regs Date: Fri, 14 Mar 2003 10:31:02 +0100 douze@enseeiht.fr writes: >>Number: 10077 >>Category: target >>Synopsis: gcc -msse2 generates movd to move dwords between xmm regs >>Confidential: no >>Severity: critical >>Priority: medium >>Responsible: unassigned >>State: open >>Class: sw-bug >>Submitter-Id: net >>Arrival-Date: Fri Mar 14 08:16:00 UTC 2003 >>Closed-Date: >>Last-Modified: >>Originator: douze@enseeiht.fr >>Release: gcc 3.2.2 on x86 >>Organization: >>Environment: > Linux 2.4.18 >>Description: > The bug appears when I compile a function with many variables. GCC then uses xmm registers as 32-bit scalar integer registers. > > When it has to move data with an xmm register involved, it generates a movd instruction, which doesn't work (movss might work better). Although there is sse2 assembly in my code, I don't think it comes from there. > > The assembler used is GNU assembler version 2.11.92.0.10 (i486-suse-linux) using BFD version 2.11.92.0.10 20011021 (SuSE) >>How-To-Repeat: > Compile the code with > > gcc -c gcc_bug.i -msse2 -O3 >>Fix: > replace movd with movss in the .s file Which instruction is generated in this case? I only see one movd generated (with not exactly the same compiler) and that one looks fine to me (and might even come from your inline assembler). Please tell us a bit more why the generated code is wrong, Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2003-03-14 9:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-14 9:36 Andreas Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-14 14:13 hubicka 2003-03-14 15:12 bangerth 2003-03-14 12:05 aj 2003-03-14 8:16 douze
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=20030314093601.32274.qmail@sources.redhat.com \ --to=aj@suse.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).