public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Richard Henderson <rth@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Use i386/crtfastmath.c on Solaris 2/x86
Date: Wed, 01 Jun 2011 17:29:00 -0000	[thread overview]
Message-ID: <ydd4o49cvf2.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4DE675B4.5040801@redhat.com> (Richard Henderson's message of	"Wed, 01 Jun 2011 10:24:04 -0700")

Richard Henderson <rth@redhat.com> writes:

> On 06/01/2011 07:51 AM, Rainer Orth wrote:
>> +  /* Set PC to the instruction after the faulting one to skip over it,
>> +     otherwise we enter an infinite loop.  4 is the size of the stmxcsr
>> +     instruction.  */
> ...
>> +      /* We need a single SSE instruction here so the handler can safely skip
>> +	 over it.  */
>> +      __asm__ volatile ("movss %xmm2,%xmm1");
>
> The comment referencing stmxcsr doesn't match the movss code.
> It's still a 4 byte opcode, so the code still works.

Copy-and-paste error ;-(  We already have the same code in
libgfortran/config/fpu-387.h and (without the comment) in
gcc/testsuite/lib/target-supports.exp.  I still mean to fix
driver-i386.c to correcly handle -march=native on Solaris 8 and 9 which
cannot in general execute SSE insns.  I wonder if there's a better place
to share this code?

> I do wonder if using "movaps %xmm0,%xmm0" might be cleaner,
> to avoid clobbering a register, even if that register is
> surely dead anyway.  That's a 3 byte opcode though, so the
> handler would need updating.

I'll give it a try.

Thanks.
        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2011-06-01 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 14:01 Rainer Orth
2011-05-31 14:23 ` Uros Bizjak
2011-06-01 14:51   ` Rainer Orth
2011-06-01 17:24     ` Richard Henderson
2011-06-01 17:29       ` Rainer Orth [this message]
2011-06-01 18:06         ` Richard Henderson
2011-06-03 17:39       ` Rainer Orth

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=ydd4o49cvf2.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.com \
    --cc=ubizjak@gmail.com \
    /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: link
Be 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).