public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/66181] [6 Regression]: /usr/include/bits/types.h:134:16: ICE: verify_type failed Date: Sun, 17 May 2015 19:41:00 -0000 [thread overview] Message-ID: <bug-66181-4-3NkiHlws3C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66181-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66181 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> --- Seen when cross-building GCC for ARM targets too. The problem appeared with r223252: 2015-05-16 Jan HUbicka <hubicka@ucw.cz> * tree.c (verify_type_variant): Verify tree_base and type_common flags. (verify_type): Verify STRING_FLAG.
next prev parent reply other threads:[~2015-05-17 19:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-66181-4@http.gcc.gnu.org/bugzilla/> 2015-05-17 9:13 ` ubizjak at gmail dot com 2015-05-17 19:41 ` clyon at gcc dot gnu.org [this message] 2015-05-17 20:54 ` danglin at gcc dot gnu.org 2015-05-18 1:41 ` sandra at gcc dot gnu.org 2015-05-18 12:42 ` rguenth at gcc dot gnu.org 2015-05-18 18:09 ` hubicka at gcc dot gnu.org 2015-05-18 21:11 ` olegendo at gcc dot gnu.org 2015-05-19 2:42 ` thopre01 at gcc dot gnu.org 2015-05-21 9:57 ` clyon at gcc dot gnu.org 2015-05-21 22:58 ` jose.marchesi at oracle dot com 2015-05-25 21:27 ` andreast at gcc dot gnu.org 2015-05-26 12:27 ` ramana at gcc dot gnu.org 2015-05-26 13:22 ` ramana at gcc dot gnu.org 2015-05-27 17:29 ` gary at intrepid dot com 2015-09-19 11:01 ` olegendo 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-66181-4-3NkiHlws3C@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).