public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: SenthilKumar.Selvaraj@microchip.com, gcc-patches@gcc.gnu.org
Cc: ro@CeBiTec.Uni-Bielefeld.DE, mikestump@comcast.net
Subject: Re: [Testsuite] Skip -fdelete-null-pointer-check tests if target keeps_null_pointer_checks
Date: Mon, 15 May 2023 22:34:55 -0600	[thread overview]
Message-ID: <3610836d-cfa9-da7f-009e-f1a94d8e25c1@gmail.com> (raw)
In-Reply-To: <595B4378-CEDC-4D6D-A6B1-7FF80AFEF7B0@microchip.com>



On 5/14/23 23:06, SenthilKumar.Selvaraj--- via Gcc-patches wrote:
> Hi,
> 
> When running regression tests related to https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616772.html,
> I noticed a bunch of failures because some tests explicitly pass in
> -fdelete-null-pointer-checks, even if the target is configured to keep them.
> 
> This patch skips such failing tests by adding a dg-skip-if for keeps_null_pointer_checks.
> Ok to commit?
> 
> Regards
> Senthil
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.dg/attr-returns-nonnull.c: Skip if
> 	keeps_null_pointer_checks.
> 	* gcc.dg/init-compare-1.c: Likewise.
> 	* gcc.dg/ipa/pr85734.c: Likewise.
> 	* gcc.dg/ipa/propmalloc-1.c: Likewise.
> 	* gcc.dg/ipa/propmalloc-2.c: Likewise.
> 	* gcc.dg/ipa/propmalloc-3.c: Likewise.
> 	* gcc.dg/ipa/propmalloc-4.c: Likewise.
> 	* gcc.dg/tree-ssa/evrp11.c: Likewise.
> 	* gcc.dg/tree-ssa/pr83648.c: Likewise.
OK.
jeff

      reply	other threads:[~2023-05-16  4:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  5:06 SenthilKumar.Selvaraj
2023-05-16  4:34 ` 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=3610836d-cfa9-da7f-009e-f1a94d8e25c1@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=SenthilKumar.Selvaraj@microchip.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).