public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Georg-Johann Lay <avr@gjlay.de>
To: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch, testsuite, applied] PR52641 Fix more fallout from sloppy tests.
Date: Sun, 7 Jan 2024 18:17:50 +0100	[thread overview]
Message-ID: <f938e368-f311-40a3-b092-b55a41d33a5f@gjlay.de> (raw)
In-Reply-To: <71920087-4b6c-48f4-8b96-5633671fd023@gmail.com>



Am 07.01.24 um 17:45 schrieb Jeff Law:
> 
> 
> On 1/7/24 08:53, Georg-Johann Lay wrote:
>> Made some tests more generic so they can pass on more targets.
>>
>> Johann
>>
>> -- 
>>
>> testsuite/52641: Fix fallout from sloppy tests.
>>
>> gcc/testsuite/
>>      PR testsuite/52641
>>      * gcc.dg/torture/pr110838.c: Use proper shift offset to get MSB 
>> or int.
>>      * gcc.dg/torture/pr112282.c: Use at least 32 bits for :20 
>> bit-fields.
>>      * gcc.dg/tree-ssa/bitcmp-5.c: Use integral type with 32 bits or 
>> more.
>>      * gcc.dg/tree-ssa/bitcmp-6.c: Same.
>>      * gcc.dg/tree-ssa/cltz-complement-max.c: Same.
>>      * gcc.dg/tree-ssa/cltz-max.c: Same.
>>      * gcc.dg/tree-ssa/if-to-switch-8.c: Use literals that fit int.
>>      * gcc.dg/tree-ssa/if-to-switch-9.c [avr]: Set 
>> case-values-threshold=3.
>>      * gcc.dg/tree-ssa/negneg-3.c: Discriminate [not] large_double.
>>      * gcc.dg/tree-ssa/phi-opt-25b.c: Use types of correct widths for
>>      __builtin_bswapN.
>>      * gcc.dg/tree-ssa/pr55177-1.c: Same.
>>      * gcc.dg/tree-ssa/popcount-max.c: Use int32_t where required.
>>      * gcc.dg/tree-ssa/pr111583-1.c: Use intptr_t as needed.
>>      * gcc.dg/tree-ssa/pr111583-2.c: Same.
> Are you checking this on other targets?  My tester just started 
> complaining about these (ft30-elf, fr30-elf), more expected as today's 
> run progresses)
> 
> 
>> Tests that now fail, but worked before (2 tests):
>>
>> ft32-sim: gcc: gcc.dg/tree-ssa/phi-opt-25b.c (test for excess errors)
>> ft32-sim: gcc: gcc.dg/tree-ssa/phi-opt-25b.c (test for excess errors)
> 
> Jeff

Hi Jeff, thanks for fixing the typo.

It slipped through because "int short" works in that place.

Usually when going after PR52641 I used dg-require, dg-skip or
dg-xfail for tests that fail on 16-bit int etc.

The take above was more ambitious in that it tried to make some
tests work without breaking other platforms of course.

It's not always easy to get the intent of a test case and how
to make it more generic though.

Johann

  reply	other threads:[~2024-01-07 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 15:53 [patch,testsuite,applied] " Georg-Johann Lay
2024-01-07 16:45 ` [patch, testsuite, applied] " Jeff Law
2024-01-07 17:17   ` Georg-Johann Lay [this message]
2024-01-07 19:10     ` Jeff Law
  -- strict thread matches above, loose matches on Subject: below --
2024-01-07 12:14 [patch,testsuite,applied] PR52641: " Georg-Johann Lay

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=f938e368-f311-40a3-b092-b55a41d33a5f@gjlay.de \
    --to=avr@gjlay.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@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).