public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to fix ICE in strip_typedefs with -Wpadded (PR c++/79900)
Date: Thu, 09 Mar 2017 22:35:00 -0000	[thread overview]
Message-ID: <CADzB+2kp+xUmpFaTU7SkTTMnn6syQS7RUFHgXbr5tQvyh=STzw@mail.gmail.com> (raw)
In-Reply-To: <20170309223231.GH3172@redhat.com>

Yep, I just checked in that change.

On Thu, Mar 9, 2017 at 5:32 PM, Marek Polacek <polacek@redhat.com> wrote:
> On Thu, Mar 09, 2017 at 10:06:53PM +0100, Jakub Jelinek wrote:
>> On Thu, Mar 09, 2017 at 12:00:48AM +0100, Marek Polacek wrote:
>> > We crash on an assert in strip_typedefs, because we find ourselves in a
>> > scenario where RESULT, the main variant of a struct, was modified in
>> > finalize_record_size (its TYPE_ALIGN changed), but its variants (T in
>> > strip_typedefs) weren't fixed-up yet; that will happen slightly later in
>> > finalize_type_size.  So there's a discrepancy that confuses the code.
>> >
>> > This patch implements what Jason suggested to me on IRC, i.e., skip the
>> > attribute handling if RESULT is complete and T isn't.
>> >
>> > Bootstrapped/regtested on x86_64-linux, ok for trunk?
>> >
>> > 2017-03-08  Marek Polacek  <polacek@redhat.com>
>> >
>> >     PR c++/79900 - ICE in strip_typedefs
>> >     * tree.c (strip_typedefs): Skip the attribute handling if T is
>> >     a variant type which hasn't been updated yet.
>> >
>> >     * g++.dg/warn/Wpadded-1.C: New test.
>> >
>> > diff --git gcc/testsuite/g++.dg/warn/Wpadded-1.C gcc/testsuite/g++.dg/warn/Wpadded-1.C
>> > index e69de29..b3f0581 100644
>> > --- gcc/testsuite/g++.dg/warn/Wpadded-1.C
>> > +++ gcc/testsuite/g++.dg/warn/Wpadded-1.C
>> > @@ -0,0 +1,22 @@
>> > +// PR c++/79900 - ICE in strip_typedefs
>> > +// { dg-do compile }
>> > +// { dg-options "-Wpadded" }
>> > +
>> > +template <class> struct A;
>> > +template <typename> struct B { // { dg-warning "padding struct size to alignment boundary" }
>> > +  long _M_off;
>> > +  int _M_state;
>> > +};
>>
>> This fails on i686-linux, there is obviously no padding of struct size to
>> alignment boundary in that case.
>
> Ah, of course...
>
>> Can't _M_state be e.g. char, then it would work at least on all targets
>> where long has alignment of at least 2 (that can be all of them)?
>> Perhaps also make _M_off long long or add a double or long double field.
>
> Like this?  Passes with -m32.
>
> 2017-03-09  Marek Polacek  <polacek@redhat.com>
>
>         * g++.dg/warn/Wpadded-1.C: Change types of struct B fields.
>
> diff --git gcc/testsuite/g++.dg/warn/Wpadded-1.C gcc/testsuite/g++.dg/warn/Wpadded-1.C
> index b3f0581..af375a4 100644
> --- gcc/testsuite/g++.dg/warn/Wpadded-1.C
> +++ gcc/testsuite/g++.dg/warn/Wpadded-1.C
> @@ -4,8 +4,8 @@
>
>  template <class> struct A;
>  template <typename> struct B { // { dg-warning "padding struct size to alignment boundary" }
> -  long _M_off;
> -  int _M_state;
> +  long long _M_off;
> +  char _M_state;
>  };
>  template <> struct A<char> { typedef B<int> pos_type; };
>  enum _Ios_Openmode {};
>
>         Marek

      reply	other threads:[~2017-03-09 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 23:01 Marek Polacek
2017-03-09  0:52 ` Jason Merrill
2017-03-09 21:06 ` Jakub Jelinek
2017-03-09 22:32   ` Marek Polacek
2017-03-09 22:35     ` Jason Merrill [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='CADzB+2kp+xUmpFaTU7SkTTMnn6syQS7RUFHgXbr5tQvyh=STzw@mail.gmail.com' \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=polacek@redhat.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).