public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98688] C++ modules support does not work on PowerPC with opaque MMA types vector_pair/vector_quad
Date: Thu, 14 Jan 2021 18:34:13 +0000	[thread overview]
Message-ID: <bug-98688-4-tDENjc5RdZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98688-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98688

--- Comment #1 from acsawdey at gcc dot gnu.org ---
I don't know if this is the right thing to do, but ignoring the opaque type
here make the ICE go away. I suspect I need to construct a module test case
using vector_pair/vector_quad to really test this though.


diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
index d2093916c9e..3ec0b04def3 100644
--- a/gcc/cp/module.cc
+++ b/gcc/cp/module.cc
@@ -8831,6 +8831,10 @@ trees_out::type_node (tree type)
       }
       break;

+    case OPAQUE_TYPE:
+      /* No additional data.  */
+      break;
+
     case OFFSET_TYPE:
       tree_node (TYPE_OFFSET_BASETYPE (type));
       break;

  reply	other threads:[~2021-01-14 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 18:22 [Bug target/98688] New: " acsawdey at gcc dot gnu.org
2021-01-14 18:34 ` acsawdey at gcc dot gnu.org [this message]
2021-01-15 13:25 ` [Bug target/98688] " nathan at gcc dot gnu.org
2021-01-15 18:01 ` acsawdey at gcc dot gnu.org
2024-03-12 13:42 ` [Bug target/98688] [modules] " cvs-commit at gcc dot gnu.org
2024-03-12 13:44 ` nshead at gcc dot gnu.org

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=bug-98688-4-tDENjc5RdZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).