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] New: ICE in vague_linkage_p, at cp/decl2.c:2041 Date: Tue, 28 Apr 2020 23:17:00 +0000 [thread overview] Message-ID: <bug-94835-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835 Bug ID: 94835 Summary: ICE in vague_linkage_p, at cp/decl2.c:2041 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: casner at acm dot org Target Milestone: --- I am working on a pdp11-elf32 target in binutils with the goal of being able to compile C++ for the PDP11 (an effort instigated by Paul Koning, gcc PDP11 maintainer). I have a first implementation running, so now I am trying to build g++ and libstdc++v3 to go with it. I am attempting to build the gcc tree with newlib and libgloss symlinked in and with the binutils components installed at the prefix and with gcc configured as follows: ../configure --target=pdp11-elf32 --prefix=/usr/local --enable-languages=c,c++ --disable-libssp --disable-libgfortran --disable-libobjc --with-gmp=/opt/local/ --with-mpfr=/opt/local/ --with-mpc=/opt/local/ --with-libiconv-prefix=/opt/local --with-newlib My host is running macOS 10.14.6. gcc and g++ build successfully, but while building libstdc++v3 I get: .../libstdc++-v3/include/chrono:544:7: internal compiler error: in vague_linkage_p, at cp/decl2.c:2041 This is with code freshly fetched with git today. 19667c82e479dc2bf8351588ed57aff90220b748
next reply other threads:[~2020-04-28 23:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-28 23:17 casner at acm dot org [this message] 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 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@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: linkBe 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).