From: Kees Cook <keescook@chromium.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Qing Zhao <qing.zhao@oracle.com>, Xi Ruoyao <xry111@xry111.site>,
Richard Biener <richard.guenther@gmail.com>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Question on -fwrapv and -fwrapv-pointer
Date: Thu, 14 Sep 2023 17:23:24 -0700 [thread overview]
Message-ID: <202309141721.1DB367E8D4@keescook> (raw)
In-Reply-To: <CA+=Sn1=KxtMYs-uOZxnfpmiMyNQ3jcVyfgnQZ_cfYxF-fpGFDA@mail.gmail.com>
On Thu, Sep 14, 2023 at 01:57:41PM -0700, Andrew Pinski wrote:
> Now -fsanitize=pointer-overflow is already there for GCC which was
> added in r8-2238-gc9b39a4955f56fe609ef5478 . LLVM/clang also provides
> it in the same timeframe too .
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80998
Ah, thanks for the link! And checking it just now it seems like Clang's
implementation doesn't work. Fun times.
-Kees
--
Kees Cook
prev parent reply other threads:[~2023-09-15 0:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 13:41 Qing Zhao
2023-09-14 14:06 ` Richard Biener
2023-09-14 15:01 ` Qing Zhao
2023-09-14 15:12 ` Richard Biener
2023-09-14 15:57 ` Qing Zhao
2023-09-14 16:18 ` Xi Ruoyao
2023-09-14 20:48 ` Qing Zhao
2023-09-14 20:57 ` Andrew Pinski
2023-09-14 21:41 ` Qing Zhao
2023-09-15 7:43 ` Xi Ruoyao
2023-09-15 15:12 ` Qing Zhao
2023-09-15 15:18 ` Andrew Pinski
2023-09-15 18:34 ` Kees Cook
2023-09-15 12:41 ` Arsen Arsenović
2023-09-15 15:24 ` Qing Zhao
2023-09-15 15:29 ` Richard Biener
2023-09-15 15:37 ` Qing Zhao
2023-09-15 16:53 ` Xi Ruoyao
2023-09-15 17:56 ` Qing Zhao
2023-09-15 17:26 ` Richard Biener
2023-09-15 17:47 ` Qing Zhao
2023-09-15 18:43 ` Kees Cook
2024-02-15 8:32 ` Fangrui Song
2024-02-15 23:31 ` Kees Cook
2023-09-15 0:23 ` Kees Cook [this message]
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=202309141721.1DB367E8D4@keescook \
--to=keescook@chromium.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=qing.zhao@oracle.com \
--cc=richard.guenther@gmail.com \
--cc=xry111@xry111.site \
/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).