public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "casner at acm dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94835] ICE in vague_linkage_p, at cp/decl2.c:2041
Date: Thu, 30 Apr 2020 04:46:26 +0000	[thread overview]
Message-ID: <bug-94835-4-l3YT2JLv4o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94835-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Stephen Casner <casner at acm dot org> ---
I verified that the compilation of chrono:544 is the first time in the build
that the failing assert is executed, so that likely implies that the problem is
general and not specific to the particular source code.

The only mentions of COMDAT in the pdp11 backend are the macros

#define TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT hook_bool_void_false
#define TARGET_CXX_LIBRARY_RTTI_COMDAT hook_bool_void_false

These are in the direction that make the assert true rather than false, so
changing those to the default hook_bool_void_true wouldn't help (and would
presumably cause something else to fail).

I'm way out of my league here, so any suggestions would be appreciated.

  parent reply	other threads:[~2020-04-30  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 23:17 [Bug c++/94835] New: " casner at acm dot org
2020-04-28 23:18 ` [Bug c++/94835] " casner at acm dot org
2020-04-28 23:27 ` casner at acm dot org
2020-04-29 15:19 ` casner at acm dot org
2020-04-30  4:46 ` casner at acm dot org [this message]
2020-05-11 22:00 ` casner at acm dot 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-94835-4-l3YT2JLv4o@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).