public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/58420] internal compiler error: in ubsan_type_descriptor, at ubsan.c:280 Date: Sat, 14 Sep 2013 08:06:00 -0000 [thread overview] Message-ID: <bug-58420-4-kQjctIwxZC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58420-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58420 --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Though, could you provide some preprocessed testcase? At any rate, I think it's because ubsan_type_descriptor doesn't handle IDENTIFIER_NODEs very well, this should be fixed as a side effect of http://gcc.gnu.org/ml/gcc-patches/2013-09/msg00917.html patch once it gets applied.
next prev parent reply other threads:[~2013-09-14 8:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-13 23:43 [Bug sanitizer/58420] New: " jan.smets@alcatel-lucent.com 2013-09-14 0:07 ` [Bug sanitizer/58420] " jan.smets@alcatel-lucent.com 2013-09-14 7:53 ` mpolacek at gcc dot gnu.org 2013-09-14 8:06 ` mpolacek at gcc dot gnu.org [this message] 2013-09-14 8:31 ` mpolacek at gcc dot gnu.org 2013-09-16 15:50 ` mpolacek at gcc dot gnu.org 2013-09-25 9:04 ` mpolacek at gcc dot gnu.org 2013-09-25 9:05 ` mpolacek 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-58420-4-kQjctIwxZC@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).