public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Jeff Law <law@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 10/10] Port testsuite to GCN
Date: Thu, 06 Dec 2018 15:27:00 -0000	[thread overview]
Message-ID: <e209773e-cfb2-399f-c72d-c4f1944810f7@codesourcery.com> (raw)
In-Reply-To: <bdc97e35-5152-778c-a192-42dbd92305a1@redhat.com>

I finally got back to investigating this ....

On 21/11/2018 01:00, Jeff Law wrote:
>> --- a/gcc/testsuite/gcc.dg/gimplefe-28.c
>> +++ b/gcc/testsuite/gcc.dg/gimplefe-28.c
>> @@ -1,5 +1,5 @@
>>   /* { dg-do compile { target sqrt_insn } } */
>> -/* { dg-options "-fgimple -O2" } */
>> +/* { dg-options "-fgimple -O2 -ffast-math" } */
> So why does the GCN need fast-math here?  I'm not aware of any other
> target  that needs that kind of handling to make this test work.

It needs it because the sqrt instruction is only enabled when 
flag_unsafe_math_optimizations is set. This seems appropriate given the 
approximate nature of the machine instruction.

This test uses gimple directly and so bypasses the usual optab checks 
that would normally select a library function instead, which results in 
an ICE.

It seems like a safe change to make, since most targets will have more 
patterns enabled, not fewer, in this mode.

The test will continue to fail on any target that does not have a sqrt 
instruction at all.

Andrew

  parent reply	other threads:[~2018-12-06 15:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:27 [PATCH 00/10] AMD GCN Port v2 Andrew Stubbs
2018-11-16 16:27 ` [PATCH 01/10] Fix IRA ICE Andrew Stubbs
2018-11-21  0:47   ` Jeff Law
2018-11-21 11:35     ` Andrew Stubbs
2018-12-08 12:15       ` Richard Sandiford
2018-12-08 16:23         ` Jeff Law
2018-12-10 15:22           ` Andrew Stubbs
2018-11-16 16:28 ` [PATCH 07/10] Add dg-require-effective-target exceptions Andrew Stubbs
2018-11-26 22:08   ` Mike Stump
2018-11-27  9:29     ` Andrew Stubbs
2018-11-16 16:28 ` [PATCH 08/10] Testsuite: GCN is always PIE Andrew Stubbs
2018-11-16 16:28 ` [PATCH 09/10] Ignore LLVM's blank lines Andrew Stubbs
2018-11-16 16:28 ` [PATCH 05/10] GCN back-end code Andrew Stubbs
2018-11-16 16:28 ` [PATCH 03/10] GCN libgcc Andrew Stubbs
2018-11-21  0:49   ` Jeff Law
2018-11-16 16:28 ` [PATCH 02/10] GCN libgfortran Andrew Stubbs
2018-11-16 16:28 ` [PATCH 04/10] GCN machine description Andrew Stubbs
2018-11-16 16:29 ` [PATCH 10/10] Port testsuite to GCN Andrew Stubbs
2018-11-21  1:01   ` Jeff Law
2018-11-26 20:04     ` Mike Stump
2018-11-26 21:13       ` Mike Stump
2018-11-27  9:27         ` Andrew Stubbs
2018-12-06 16:10         ` Andrew Stubbs
2018-12-06 15:27     ` Andrew Stubbs [this message]
2018-12-08 12:05       ` Richard Sandiford
2018-11-16 16:29 ` [PATCH 06/10] GCN back-end config Andrew Stubbs
2018-11-16 17:44   ` Joseph Myers
2018-11-20 11:44     ` Andrew Stubbs
2018-11-21  2:32   ` Jeff Law

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=e209773e-cfb2-399f-c72d-c4f1944810f7@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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).