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: Wed, 29 Apr 2020 15:19:15 +0000	[thread overview]
Message-ID: <bug-94835-4-s2FSaEwXQF@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 #3 from Stephen Casner <casner at acm dot org> ---
I'm working with unmodified gcc sources, but if no other targets are seeing
this problem then it may be caused by pdp11-specific code somewhere else.  I
guess that g++ and libstdc++v3 have never been successfully built for pdp11.

Any suggestions for debugging this?  Perhaps backing off on some compiler
feature that might be tickling the bug?

  parent reply	other threads:[~2020-04-29 15:19 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 [this message]
2020-04-30  4:46 ` casner at acm dot org
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-s2FSaEwXQF@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).