public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Turn some compile-time tests into run-time tests
Date: Thu, 28 Apr 2016 14:59:00 -0000	[thread overview]
Message-ID: <188b3046-c236-02c4-0b5a-ce25388aafc2@redhat.com> (raw)
In-Reply-To: <CA+C-WL9u0EZ7S6qHN_QEiWKc1G7gOXu=HWCyOrrmifK9AF39EA@mail.gmail.com>

On 04/28/2016 08:03 AM, Patrick Palka wrote:

>>
>> The rest seem OK to me.  Note that I'm not convinced all these tests were
>> designed to be execution tests, even though they use __builtin_abort and
>> friends.  Though it's a good marker of something that can/should be looked
>> at.
>
> True..  What made me look into this in the first place is that I
> caught myself making a similar mistake, i.e. marking an execution test
> case as dg-do compile instead of dg-do run out of habit.
It's an easy mistake to make and, it's pretty low in terms of real world 
impact :-)


  But I
> suppose it's worth looking at the context of each of these tests to
> see if they were not actually intended to be execution tests.  I'll
> double check this and report back; in the meantime I also found some
> more tests that ought to be looked at.
I think for the set you already identified go ahead and make the 
approved changes.  We don't really lose anything by doing so.  Going 
forward we just have to continue to watch for this kind of thing 
slipping through the cracks and updating tests as mistakes are identified.

jeff

      reply	other threads:[~2016-04-28 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 23:39 Patrick Palka
2016-03-10 23:54 ` Patrick Palka
2016-03-11 16:39 ` Patrick Palka
2016-04-27 21:26   ` Jeff Law
2016-04-27 21:37 ` Jeff Law
2016-04-28 14:03   ` Patrick Palka
2016-04-28 14:59     ` Jeff Law [this message]

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=188b3046-c236-02c4-0b5a-ce25388aafc2@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=patrick@parcs.ath.cx \
    /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).