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/63956] [5 Regression][UBSAN] ICE segfault in cxx_eval_call_expression ../../gcc/cp/constexpr.c Date: Wed, 19 Nov 2014 22:37:00 -0000 [thread overview] Message-ID: <bug-63956-4-LHdcEBPc4I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63956 --- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Earlier today I tried the following and it seemed to work, but I don't know constexpr.c, so it may be totally bogus. --- gcc/cp/constexpr.c +++ gcc/cp/constexpr.c @@ -1149,6 +1149,10 @@ cxx_eval_call_expression (const constexpr_ctx *ctx, tree t, constexpr_call *entry; bool depth_ok; + if (fun == NULL_TREE + && CALL_EXPR_IFN (t) == IFN_UBSAN_NULL) + return t; + if (TREE_CODE (fun) != FUNCTION_DECL) { /* Might be a constexpr function pointer. */
next prev parent reply other threads:[~2014-11-19 22:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-19 11:19 [Bug sanitizer/63956] New: " burnus at gcc dot gnu.org 2014-11-19 11:27 ` [Bug sanitizer/63956] " mpolacek at gcc dot gnu.org 2014-11-19 11:34 ` mpolacek at gcc dot gnu.org 2014-11-19 12:15 ` jakub at gcc dot gnu.org 2014-11-19 22:09 ` jason at gcc dot gnu.org 2014-11-19 22:12 ` jakub at gcc dot gnu.org 2014-11-19 22:37 ` mpolacek at gcc dot gnu.org [this message] 2014-11-19 22:42 ` jakub at gcc dot gnu.org 2014-11-19 22:54 ` mpolacek at gcc dot gnu.org 2014-11-20 7:18 ` jakub at gcc dot gnu.org 2014-11-20 16:13 ` mpolacek at gcc dot gnu.org 2014-11-20 16:15 ` jakub at gcc dot gnu.org 2014-11-20 16:22 ` mpolacek at gcc dot gnu.org 2014-12-01 15:30 ` mpolacek at gcc dot gnu.org 2014-12-01 15:31 ` 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-63956-4-LHdcEBPc4I@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).