From: Richard Biener <richard.guenther@gmail.com>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PING][PATCH] c: Handle initializations of opaque types [PR106016] (need review of expr.cc hunk)
Date: Tue, 26 Jul 2022 08:57:20 +0200 [thread overview]
Message-ID: <CAFiYyc0R0=xQofaixX-hXQ1h6VEdDJTcuEgyoZXkF87Y=sPKoA@mail.gmail.com> (raw)
In-Reply-To: <892eb3fe-617d-1b39-fae9-32c68ed8b1f9@linux.ibm.com>
On Tue, Jul 26, 2022 at 12:46 AM Peter Bergner via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> I'd like to ping the following patch. Segher has approved the
> test case change, so I just need a review for the expr.cc change.
>
> Peter
>
>
>
> Message-ID: <009c391d-3994-8755-0d22-9e80faf91f42@linux.ibm.com>
> Date: Fri, 17 Jun 2022 23:50:35 -0500
> To: GCC Patches <gcc-patches@gcc.gnu.org>
> Subject: [PATCH] c: Handle initializations of opaque types [PR106016]
>
>
> On 6/17/22 11:50 PM, Peter Bergner via Gcc-patches wrote:
> > The initial commit that added opaque types thought that there couldn't
> > be any valid initializations for variables of these types, but the test
> > case in the bug report shows that isn't true. The solution is to handle
> > OPAQUE_TYPE initializations just like the other scalar types.
> >
> > This passed bootstrap and regtesting with no regressions on powerpc64le-linux.
> > Ok for trunk? This is an issue in GCC 12 and 11 too. Ok for the release
> > branches after some burn-in on trunk?
OK.
Richard.
> > Peter
> >
> > gcc/
> > PR c/106016
> > * expr.cc (count_type_elements): Handle OPAQUE_TYPE.
> >
> > gcc/testsuite/
> > PR c/106016
> > * gcc.target/powerpc/pr106016.c: New test.
> >
> > diff --git a/gcc/expr.cc b/gcc/expr.cc
> > index 78c839ab425..1675198a146 100644
> > --- a/gcc/expr.cc
> > +++ b/gcc/expr.cc
> > @@ -6423,13 +6423,13 @@ count_type_elements (const_tree type, bool for_ctor_p)
> > case OFFSET_TYPE:
> > case REFERENCE_TYPE:
> > case NULLPTR_TYPE:
> > + case OPAQUE_TYPE:
> > return 1;
> >
> > case ERROR_MARK:
> > return 0;
> >
> > case VOID_TYPE:
> > - case OPAQUE_TYPE:
> > case METHOD_TYPE:
> > case FUNCTION_TYPE:
> > case LANG_TYPE:
> > diff --git a/gcc/testsuite/gcc.target/powerpc/pr106016.c b/gcc/testsuite/gcc.target/powerpc/pr106016.c
> > new file mode 100644
> > index 00000000000..3db8345dcc6
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/powerpc/pr106016.c
> > @@ -0,0 +1,14 @@
> > +/* PR target/106016 */
> > +/* { dg-require-effective-target power10_ok } */
> > +/* { dg-options "-O2 -mdejagnu-cpu=power10" } */
> > +
> > +/* Make sure we do not ICE on the following test case. */
> > +
> > +extern void bar (__vector_quad *);
> > +
> > +void
> > +foo (__vector_quad *a, __vector_quad *b)
> > +{
> > + __vector_quad arr[2] = {*a, *b};
> > + bar (&arr[0]);
> > +}
>
next prev parent reply other threads:[~2022-07-26 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 4:50 [PATCH] c: Handle initializations of opaque types [PR106016] Peter Bergner
2022-06-18 14:58 ` Segher Boessenkool
2022-07-25 22:45 ` [PING][PATCH] c: Handle initializations of opaque types [PR106016] (need review of expr.cc hunk) Peter Bergner
2022-07-26 6:57 ` Richard Biener [this message]
2022-07-26 15:07 ` Peter Bergner
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='CAFiYyc0R0=xQofaixX-hXQ1h6VEdDJTcuEgyoZXkF87Y=sPKoA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/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).