From: Patrick Palka <ppalka@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Patrick Palka <ppalka@redhat.com>,
gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH] c++ modules: ICE with bitfield member in class template
Date: Fri, 7 Oct 2022 11:54:12 -0400 (EDT) [thread overview]
Message-ID: <0c9897ef-2817-0e4d-b7b0-c4f128ad97f6@idea> (raw)
In-Reply-To: <e6d21fb8-affa-7b7c-f8c1-fbaa8cc72d73@acm.org>
On Fri, 7 Oct 2022, Nathan Sidwell wrote:
> On 10/7/22 11:09, Patrick Palka wrote:
> > According to grokbitfield, DECL_BITFIELD_REPRESENTATIVE may "temporarily"
> > contain the width of the bitfield until we layout the class type (after
> > which it'll contain a FIELD_DECL). But for a class template, it'll always
> > be the width since we don't/can't layout dependent types.
> >
> > Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
>
> ok, but could you add a comment on why it might not be a decl?
Thanks a lot, I added a comment and committed the following:
-- >8 --
Subject: [PATCH] c++ modules: ICE with bitfield in class template
According to grokbitfield, DECL_BIT_FIELD_REPRESENTATIVE may temporarily
contain the width of the bitfield until we layout the class type (after
which it'll contain a decl). Thus for a bitfield in a class template
it'll always be the width, and this patch makes us avoid ICEing from
mark_class_def in this case.
gcc/cp/ChangeLog:
* module.cc (trees_out::mark_class_def): Guard against
DECL_BIT_FIELD_REPRESENTATIVE not being a decl.
gcc/testsuite/ChangeLog:
* g++.dg/modules/bfield-3.H: New test.
---
gcc/cp/module.cc | 6 +++++-
gcc/testsuite/g++.dg/modules/bfield-3.H | 8 ++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 gcc/testsuite/g++.dg/modules/bfield-3.H
diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
index cb1929bc5d5..a7c199c00a4 100644
--- a/gcc/cp/module.cc
+++ b/gcc/cp/module.cc
@@ -11919,7 +11919,11 @@ trees_out::mark_class_def (tree defn)
mark_class_member (member);
if (TREE_CODE (member) == FIELD_DECL)
if (tree repr = DECL_BIT_FIELD_REPRESENTATIVE (member))
- mark_declaration (repr, false);
+ /* If we're marking a class template definition, then
+ DECL_BIT_FIELD_REPRESENTATIVE will contain the width
+ instead of a decl (as set by grokbitfield). */
+ if (DECL_P (repr))
+ mark_declaration (repr, false);
}
/* Mark the binfo hierarchy. */
diff --git a/gcc/testsuite/g++.dg/modules/bfield-3.H b/gcc/testsuite/g++.dg/modules/bfield-3.H
new file mode 100644
index 00000000000..4fd4db7116a
--- /dev/null
+++ b/gcc/testsuite/g++.dg/modules/bfield-3.H
@@ -0,0 +1,8 @@
+// { dg-additional-options -fmodule-header }
+// { dg-module-cmi {} }
+
+template<int N>
+struct A {
+ int x : 1;
+ int y : N;
+};
--
2.38.0.rc2
prev parent reply other threads:[~2022-10-07 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 15:09 Patrick Palka
2022-10-07 15:23 ` Nathan Sidwell
2022-10-07 15:54 ` Patrick Palka [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=0c9897ef-2817-0e4d-b7b0-c4f128ad97f6@idea \
--to=ppalka@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.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).