public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46862] ICE on std::decimal::decimal32 without any fields
Date: Thu, 09 Dec 2010 18:42:00 -0000	[thread overview]
Message-ID: <bug-46862-4-qAWrDDIVig@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46862-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46862

--- Comment #2 from Janis Johnson <janis at gcc dot gnu.org> 2010-12-09 18:42:13 UTC ---
TYPE_TRANSPARENT_AGGR is set in begin_class_definition in semantics.c for the
classes std::decimal::decimal{32|64|128}. It assumes that they are defined as
in the GNU Standard C++ Library. That code should probably ICE with a good
message if there is no first field or if the first field doesn't have an
expected type.  If that sounds appropriate I can write a patch.

The C++ compiler would have to know details of other implementations of the
decimal classes in order to pass them as the underlying scalar types.


  parent reply	other threads:[~2010-12-09 18:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 11:20 [Bug c++/46862] New: " jakub at gcc dot gnu.org
2010-12-09 11:25 ` [Bug c++/46862] " jakub at gcc dot gnu.org
2010-12-09 18:42 ` janis at gcc dot gnu.org [this message]
2010-12-09 18:46 ` jakub at gcc dot gnu.org
2010-12-09 18:50 ` janis at gcc dot gnu.org
2010-12-15  4:00 ` janis at gcc dot gnu.org
2011-08-22 10:43 ` jakub at gcc dot gnu.org
2011-08-22 11:58 ` jakub at gcc dot gnu.org
2011-08-22 18:53 ` pthaugen at gcc dot gnu.org
2011-08-23 13:24 ` jakub at gcc dot gnu.org
2011-08-23 13:25 ` jakub at gcc dot gnu.org
2011-08-23 13:30 ` jakub at gcc dot gnu.org
2011-09-08 18:11 ` bergner 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-46862-4-qAWrDDIVig@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).