From: Richard Biener <richard.guenther@gmail.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: Richard Biener <rguenther@suse.de>,
Martin Sebor <msebor@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Kito Cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH] testsuite/102690: Only check warning for lp64 in Warray-bounds-16.C
Date: Thu, 30 Jun 2022 08:52:43 +0200 [thread overview]
Message-ID: <CAFiYyc2R6Gi2OGas1P+gYYqUNPK28LhAyKSuW2MX3p9pW2jfnw@mail.gmail.com> (raw)
In-Reply-To: <CALLt3ThrXArgs_pLXVHT-gkv78EgonTf0YociY8R9KvxD8zS3g@mail.gmail.com>
On Thu, Jun 30, 2022 at 4:17 AM Kito Cheng <kito.cheng@sifive.com> wrote:
>
> Committed to trunk, thanks :)
>
> Is it OK for gcc-11 and gcc-12 branches?
Yes, if the same failure is corrected there
> On Wed, Jun 29, 2022 at 5:00 PM Richard Biener <rguenther@suse.de> wrote:
> >
> > On Tue, 28 Jun 2022, Kito Cheng wrote:
> >
> > > That warning won't happen on ilp32 targets, seems like Andrew Pinski
> > > already mention that[1] before.
> > >
> > > Verified on riscv32-unknown-elf and riscv64-unknown-elf.
> > >
> > > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879#c1
> >
> > OK
> >
> > > gcc/testsuite/ChangeLog:
> > >
> > > PR testsuite/102690
> > > * g++.dg/warn/Warray-bounds-16.C: XFAIL only on lp64 for the
> > > warning.
> > > ---
> > > gcc/testsuite/g++.dg/warn/Warray-bounds-16.C | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
> > > index 89cbadb91c7..45a14b19ea3 100644
> > > --- a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
> > > +++ b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
> > > @@ -19,7 +19,7 @@ struct S
> > > p = (int*) new unsigned char [sizeof (int) * m];
> > >
> > > for (int i = 0; i < m; i++)
> > > - new (p + i) int (); /* { dg-bogus "bounds" "pr102690" { xfail *-*-* } } */
> > > + new (p + i) int (); /* { dg-bogus "bounds" "pr102690" { xfail lp64 } } */
> > > }
> > > };
> > >
> > >
> >
> > --
> > Richard Biener <rguenther@suse.de>
> > SUSE Software Solutions Germany GmbH, Frankenstra
prev parent reply other threads:[~2022-06-30 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 13:39 Kito Cheng
2022-06-29 9:00 ` Richard Biener
2022-06-30 2:16 ` Kito Cheng
2022-06-30 6:52 ` 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=CAFiYyc2R6Gi2OGas1P+gYYqUNPK28LhAyKSuW2MX3p9pW2jfnw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=msebor@redhat.com \
--cc=rguenther@suse.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).