public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Fix 2 for PR92661, Do not define builtins that overload disabled builtins
Date: Wed, 04 Dec 2019 20:51:00 -0000	[thread overview]
Message-ID: <20191204205057.GC3152@gate.crashing.org> (raw)
In-Reply-To: <4e90e982-6153-0009-c557-f963f41a0427@linux.ibm.com>

On Wed, Dec 04, 2019 at 01:56:45PM -0600, Peter Bergner wrote:
> On 12/4/19 1:16 PM, Segher Boessenkool wrote:
> > Why do you need/want the check_effective_target_dfp test?  If for example
> > this is to prevent ICEs, that is no good, that is *hiding* problems.
> > 
> > I suspect it is to stop the testsuite from complaining if you configure
> > with --disable-decimal-float.  What is different there then, compared to
> > targets that do actually not support decimal float?
> 
> Well, yes.  I saw those tests being run for my --disable-decimal-float
> runs, which resulted in FAILs for all of those tests.  They had ICE's
> on unpatched trunk and FAILed gracefully using my patch, but they all
> still FAILed, since these are DFP tests and DFP is disabled.
> There's no sense in running these tests when DFP is disabled, either
> manually due to --disable-decimal-float or implicitly because of the
> specific target.

It would be nice to keep *some* dfp test(s) to make sure we don't ICE.
If we disabled all such tests already, like with this patch, we wouldn't
have ICEd or seen this problem.  That can be a separate test of course
(and could be outside gcc.target/powerpc/dfp/).

OTOH, if you add this check, we can lose the

/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-skip-if "" { powerpc*-*-aix* } } */

from all the dtstsfi-* tests, etc.  (Well, no, need to keep the p9 part).

Making such changes to the testsuite needs testing on *all* subtargets :-(

> Why isn't just testing check_effective_target_dfp enough to disable the
> tests on Darwin, --disable-decimal-float, etc.?  That would seem to imply
> that one of those targets we're testing against enables DFP, but somehow
> we don't want to run the tests or they all still FAIL for some reason???

It should be enough.  Currently we just directly skip all tests on OSes
that do not support DFP, but that is not as nice as the effective target.


Segher

  parent reply	other threads:[~2019-12-04 20:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6129bc8a-18f3-3c25-22c0-f26e4358c5b3@linux.ibm.com>
2019-12-04 19:16 ` Segher Boessenkool
2019-12-04 19:57   ` Peter Bergner
2019-12-04 20:47     ` Iain Sandoe
2019-12-04 21:40       ` Peter Bergner
2019-12-04 22:59         ` Segher Boessenkool
2019-12-04 22:58       ` Segher Boessenkool
2019-12-04 20:51     ` Segher Boessenkool [this message]
2019-12-04 21:53       ` Peter Bergner
2019-12-04 23:03         ` Segher Boessenkool
2019-12-05  8:45           ` Iain Sandoe
2019-12-05 16:06             ` Peter Bergner
2019-12-06 23:12             ` Segher Boessenkool
2019-12-09 20:16               ` Peter Bergner
2019-12-12  9:23                 ` Segher Boessenkool
2019-12-10 18:27           ` Peter Bergner
2019-12-10 19:12             ` Peter Bergner
2019-12-10 19:59               ` Iain Sandoe
2019-12-18 14:19             ` Segher Boessenkool
2019-12-18 15:31               ` Peter Bergner

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=20191204205057.GC3152@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@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: 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).