public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/65000] ICE in in expand_builtin_eh_common, at except.c:2072 Date: Tue, 10 Feb 2015 17:53:00 -0000 [thread overview] Message-ID: <bug-65000-4-NhF2GkeWpz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65000-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65000 Richard Henderson <rth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rth at gcc dot gnu.org --- Comment #10 from Richard Henderson <rth at gcc dot gnu.org> --- Created attachment 34715 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34715&action=edit proposed patch Yes, marking the regions of __builtin_eh_copy_values sounds reasonable (and yes, it does fix the ICE here). I think it would be valuable to know what's different about ubsan that we haven't seen this same ICE with plain C++. I may spend a little bit of time trying to reverse-engineer such a test case while this patch goes through normal regression testing.
next prev parent reply other threads:[~2015-02-10 17:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65000-4@http.gcc.gnu.org/bugzilla/> 2015-02-10 13:12 ` mpolacek at gcc dot gnu.org 2015-02-10 13:44 ` larsbj at gullik dot net 2015-02-10 13:55 ` trippels at gcc dot gnu.org 2015-02-10 14:05 ` jakub at gcc dot gnu.org 2015-02-10 14:10 ` larsbj at gullik dot net 2015-02-10 14:17 ` mpolacek at gcc dot gnu.org 2015-02-10 16:18 ` jakub at gcc dot gnu.org 2015-02-10 17:53 ` rth at gcc dot gnu.org [this message] 2015-02-11 8:45 ` jakub at gcc dot gnu.org 2015-02-11 17:05 ` rth at gcc dot gnu.org 2015-02-11 17:26 ` rth at gcc dot gnu.org 2015-02-12 21:31 ` jakub 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-65000-4-NhF2GkeWpz@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).