public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97145] Sanitizer pointer-subtract breaks constexpr functions subtracting pointers Date: Mon, 05 Oct 2020 08:24:44 +0000 [thread overview] Message-ID: <bug-97145-4-DXOeWWAmJ2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97145-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97145 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:3f56563cf84f97ef271ef0f949a571c13cdd06e2 commit r10-8850-g3f56563cf84f97ef271ef0f949a571c13cdd06e2 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Sep 22 21:06:32 2020 +0200 c++: Ignore __sanitizer_ptr_{sub,cmp} builtin calls during constant expression evaluation [PR97145] These two builtin calls are added already during parsing before pointer subtractions or comparisons, normally they perform runtime verification of whether the pointers point to the same object or different objects, but during constant expressione valuation we don't really need those builtins for anything. 2020-09-22 Jakub Jelinek <jakub@redhat.com> PR c++/97145 * constexpr.c (cxx_eval_builtin_function_call): Return void_node for calls to __sanitize_ptr_{sub,cmp} builtins. * g++.dg/asan/pr97145.C: New test. (cherry picked from commit bc13106e0414b86af8f6878e7681e6a959921b9e)
next prev parent reply other threads:[~2020-10-05 8:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 11:55 [Bug c++/97145] New: " chfast at gmail dot com 2020-09-21 12:09 ` [Bug c++/97145] " rguenth at gcc dot gnu.org 2020-09-21 12:12 ` jakub at gcc dot gnu.org 2020-09-21 15:47 ` jakub at gcc dot gnu.org 2020-09-22 19:08 ` cvs-commit at gcc dot gnu.org 2020-10-05 8:24 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-23 17:34 ` chfast at gmail dot com
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-97145-4-DXOeWWAmJ2@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).