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 c/51321] __builtin_types_compatible_p (any_type_t[1][], any_other_type_t) crashes GCC Date: Tue, 29 Nov 2011 08:14:00 -0000 [thread overview] Message-ID: <bug-51321-4-f6avbX4rLu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51321-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51321 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |pinskia at gcc dot gnu.org |gnu.org | --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-11-29 05:28:24 UTC --- Semi-obvious patch: Index: c-parser.c =================================================================== --- c-parser.c (revision 181796) +++ c-parser.c (working copy) @@ -6568,9 +6568,16 @@ c_parser_postfix_expression (c_parser *p "expected %<)%>"); { tree e1, e2; + e1 = groktypename (t1, NULL, NULL); + e2 = groktypename (t2, NULL, NULL); + if (e1 == error_mark_node || e2 == error_mark_node) + { + expr.value = error_mark_node; + break; + } - e1 = TYPE_MAIN_VARIANT (groktypename (t1, NULL, NULL)); - e2 = TYPE_MAIN_VARIANT (groktypename (t2, NULL, NULL)); + e1 = TYPE_MAIN_VARIANT (e1); + e2 = TYPE_MAIN_VARIANT (e2); expr.value = comptypes (e1, e2) ? integer_one_node : integer_zero_node;
next prev parent reply other threads:[~2011-11-29 5:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-27 8:37 [Bug c/51321] New: " hnarkaytis at gmail dot com 2011-11-27 10:19 ` [Bug c/51321] " hnarkaytis at gmail dot com 2011-11-29 7:09 ` pinskia at gcc dot gnu.org 2011-11-29 8:14 ` pinskia at gcc dot gnu.org [this message] 2011-11-30 20:04 ` pinskia at gcc dot gnu.org 2011-11-30 20:07 ` 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-51321-4-f6avbX4rLu@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).