public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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 12:15:00 -0000	[thread overview]
Message-ID: <bug-63956-4-oJhmxuUAym@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Supposedly with the C++14 constexpr changes we need to be prepared to handle
all the ubsan builtins and internal calls we create during genericization.
Already in the still pending -fsanitize=vptr patch I had to deal with handling
the ubsan vptr type cache miss builtin even before the C++14 constexpr changes,
because that is created during static_cast handling, but if we now look at
DECL_SAVED_TREE, it can see all the builtins / internal calls in there.
I hope most of the ubsan stuff can be ignored for constexpr purposes.


  parent reply	other threads:[~2014-11-19 12:15 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 [this message]
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
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-oJhmxuUAym@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: link
Be 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).