public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/68010] ICE with -g and using namespace and namespace alias Date: Fri, 13 Aug 2021 21:46:57 +0000 [thread overview] Message-ID: <bug-68010-4-YFhwMMB6Fu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68010-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68010 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|internal compiler error: in |ICE with -g and using |tree_to_shwi, at |namespace and namespace |tree.h:3661 |alias Target| |x86_64-linux-gnu Last reconfirmed|2015-10-18 00:00:00 |2021-8-13 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced slightly more: namespace boost {} template <typename> struct C { }; template <typename Skipper> struct StructDecoder : C<Skipper> { StructDecoder() { namespace bs = boost; using namespace bs; } }; void NFGParserparse() { StructDecoder<int> q_syslog_desc; } Still ICEs on the trunk
next prev parent reply other threads:[~2021-08-13 21:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-18 18:33 [Bug c++/68010] New: internal compiler error: in tree_to_shwi, at tree.h:3661 ghoort1 at gmail dot com 2015-10-18 19:02 ` [Bug c++/68010] " ghoort1 at gmail dot com 2015-10-18 19:23 ` trippels at gcc dot gnu.org 2015-10-18 19:53 ` ghoort1 at gmail dot com 2015-10-18 20:18 ` [Bug debug/68010] " trippels at gcc dot gnu.org 2015-10-19 17:43 ` trippels at gcc dot gnu.org 2015-10-21 20:15 ` ghoort1 at gmail dot com 2015-10-22 7:48 ` trippels at gcc dot gnu.org 2021-08-13 21:46 ` pinskia at gcc dot gnu.org [this message] 2024-03-25 5:25 ` [Bug debug/68010] [11/12/13/14 Regression] ICE with -g and using namespace and namespace alias inside a template class with dependent inheritance pinskia 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-68010-4-YFhwMMB6Fu@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).