public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/66241] [6 regression] [ARM] ICE: verify_type failed while building libstdc++ (dwarfout.c: gen_type_die_with_usage()) Date: Thu, 21 May 2015 17:45:00 -0000 [thread overview] Message-ID: <bug-66241-4-RzMlXORnOV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66241-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66241 --- Comment #3 from Vidya Praveen <vp at gcc dot gnu.org> --- And this change seems to be the cause: Author: hubicka Date: Sat May 16 20:51:50 2015 New Revision: 223252 URL: https://gcc.gnu.org/viewcvs?rev=223252&root=gcc&view=rev Log: * tree.c (verify_type_variant): Verify tree_base and type_common flags. (verify_type): Verify STRING_FLAG. Modified: trunk/gcc/ChangeLog trunk/gcc/tree.c
next prev parent reply other threads:[~2015-05-21 17:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-21 12:57 [Bug middle-end/66241] New: " vp at gcc dot gnu.org 2015-05-21 12:59 ` [Bug middle-end/66241] " vp at gcc dot gnu.org 2015-05-21 15:46 ` [Bug middle-end/66241] [6 regression] [ARM] " ramana at gcc dot gnu.org 2015-05-21 17:45 ` vp at gcc dot gnu.org [this message] 2015-05-26 12:27 ` ramana 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-66241-4-RzMlXORnOV@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).