public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch gcc13] middle-end/70090: Dynamic sizes for -fsanitize=object-size
Date: Mon, 9 May 2022 13:02:07 +0530	[thread overview]
Message-ID: <783f109c-b8ad-a22c-e808-8252973f6986@gotplt.org> (raw)
In-Reply-To: <20220207120704.GW2646553@tucnak>

On 07/02/2022 17:37, Jakub Jelinek wrote:
> On Mon, Feb 07, 2022 at 05:31:58PM +0530, Siddhesh Poyarekar wrote:
>> Use __builtin_dynamic_object_size to get object sizes for ubsan.
>>
>> gcc/ChangeLog:
>>
>> 	middle-end/70090
>> 	* ubsan.cc (ubsan_expand_objsize_ifn): Allow non-constant SIZE.
>> 	(instrument_object_size): Get dynamic object size expression.
>>
>> gcc/testsuite/ChangeLog:
>>
>> 	middle-end/70090
>> 	* gcc.dg/ubsan/object-size-dyn.c: New test.
>>
>> Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
>> ---
>> Proposing for gcc13 since I reckoned this is not feasible for stage 4.
> 
> Ok for stage1.
> 
> 	Jakub
> 

Hi Jakub, may I rebase and push this now?

Thanks,
Siddhesh

  reply	other threads:[~2022-05-09  7:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 12:01 Siddhesh Poyarekar
2022-02-07 12:07 ` Jakub Jelinek
2022-05-09  7:32   ` Siddhesh Poyarekar [this message]
2022-05-09  7:37     ` Jakub Jelinek
2022-05-10 10:46       ` Martin Liška
2022-05-10 16:35         ` Siddhesh Poyarekar
2022-05-11  2:11         ` [PATCH] middle-end/70090: Register __bdos for sanitizers if necessary Siddhesh Poyarekar
2022-05-11  6:04           ` Jakub Jelinek

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=783f109c-b8ad-a22c-e808-8252973f6986@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).