public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/113151] Need for a TBAA / strict aliasing sanitizer (TySan)
Date: Mon, 08 Jan 2024 14:08:47 +0000	[thread overview]
Message-ID: <bug-113151-4-dUfH23zJh3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113151-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113151

Richard Biener <rguenth at gcc dot gnu.org> changed:

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
IIRC Jakub tried to implement something at some point.

Note what's needed is runtime tracking of the effective dynamic type of
objects (memory) and enforcing access rules.  Language frontend rules
are not 1:1 compatible and the middle-end implements something common.

It's going to be difficult when not the whole program including runtime
is instrumented.

  parent reply	other threads:[~2024-01-08 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 18:47 [Bug sanitizer/113151] New: " sjames at gcc dot gnu.org
2023-12-26 20:20 ` [Bug sanitizer/113151] " xry111 at gcc dot gnu.org
2024-01-08 14:08 ` rguenth at gcc dot gnu.org [this message]
2024-01-08 14:21 ` 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-113151-4-dUfH23zJh3@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).