public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: Aldy Hernandez <aldyh@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: XFAIL bogus g++.dg/warn/Wstringop-overflow-4.C:144, PR106120
Date: Thu, 9 Feb 2023 08:27:57 +0100	[thread overview]
Message-ID: <CAFiYyc0Sv+HuvVez0eghXAGh=xWahN2TAwwq=7uv-JLz7GUbbQ@mail.gmail.com> (raw)
In-Reply-To: <20230207180342.53BCB2042C@pchp3.se.axis.com>

On Tue, Feb 7, 2023 at 7:04 PM Hans-Peter Nilsson via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> > From: Aldy Hernandez <aldyh@redhat.com>
> > Date: Tue, 7 Feb 2023 17:52:02 +0100
>
> > Up to the release managers, but I have no objections.
>
> I take it that's for both patches.  Thanks!
> (Potential reviewers: these patches are local to the testsuite.)

OK

> brgds, H-P
>
>
> >
> > Aldy
> >
> > On 2/7/23 17:50, Hans-Peter Nilsson wrote:
> > > (sort-of-ping:) Aldy, I missed CC:ing you on the similar
> > > https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611206.html
> > > would you mind having a look?
> > >
> > > Tested native x86_64-pc-linux-gnu (w/wo. -m32) and cris-elf.
> > > Ok to commit?
> > >
> > > ---- 8< ----
> > > There was a commit r13-2082-gbf13a13c65bd06 "c++: remove some xfails"
> > > (not referencing the PR) that dealt with part of the PR, but didn't
> > > xfail the ilp32-specific (bogus) warning mentioned in the PR.
> > >
> > >     PR testsuite/106120
> > >     * g++.dg/warn/Wstringop-overflow-4.C:144 XFAIL bogus warning for
> > >     ilp32 targets with c++98.
> > > ---
> > >   gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C b/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
> > > index 3716d2d13be0..35fb59e02320 100644
> > > --- a/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
> > > +++ b/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
> > > @@ -141,7 +141,7 @@ void test_strcpy_new_int16_t (size_t n, const size_t vals[])
> > >
> > >     int r_imin_imax = SR (INT_MIN, INT_MAX);
> > >     T (S (1), new int16_t[r_imin_imax]);
> > > -  T (S (2), new int16_t[r_imin_imax + 1]);
> > > +  T (S (2), new int16_t[r_imin_imax + 1]); // { dg-bogus "into a region of size" "pr106120" { xfail { ilp32 && c++98_only } } }
> > >     T (S (9), new int16_t[r_imin_imax * 2 + 1]);
> > >
> > >     int r_0_imax = SR (0, INT_MAX);
> >

      reply	other threads:[~2023-02-09  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 16:50 Hans-Peter Nilsson
2023-02-07 16:52 ` Aldy Hernandez
2023-02-07 18:03   ` Hans-Peter Nilsson
2023-02-09  7:27     ` Richard Biener [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='CAFiYyc0Sv+HuvVez0eghXAGh=xWahN2TAwwq=7uv-JLz7GUbbQ@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@axis.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).