public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Cc: fweimer@redhat.com
Subject: Re: [PATCH] Enable _FORTIFY_SOURCE=3 for gcc 12 and above
Date: Wed, 12 Jan 2022 09:44:32 +0530	[thread overview]
Message-ID: <4da0567f-deee-bd87-14d3-ece15aff5091@sourceware.org> (raw)
In-Reply-To: <d5ce67c8-d43c-90c6-8c06-cee382d34c3f@linaro.org>

On 17/12/2021 18:47, Adhemerval Zanella via Libc-alpha wrote:
> 
> 
> On 17/12/2021 01:07, Siddhesh Poyarekar via Libc-alpha wrote:
>> gcc 12 now has support for the __builtin_dynamic_object_size builtin.
>> Adapt the macro checks to enable _FORTIFY_SOURCE=3 on gcc 12 and above.
>>
>> Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
> 
> With gcc version 12.0.0 20211217 (experimental) [master r12-6038-g411ac94611f]
> I am seeing two new failures:
> 
>    FAIL: debug/tst-chk7
>    FAIL: debug/tst-chk8

This should now work on gcc trunk as of r12-6482, tested with:

gcc version 12.0.0 20220112 (experimental) (GCC)

OK to commit?

Thanks,
Siddhesh

  parent reply	other threads:[~2022-01-12  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  4:07 Siddhesh Poyarekar
2021-12-17 13:17 ` Adhemerval Zanella
2021-12-17 13:54   ` Siddhesh Poyarekar
2021-12-17 15:24     ` Siddhesh Poyarekar
2021-12-17 19:04       ` Adhemerval Zanella
2021-12-17 19:30         ` Siddhesh Poyarekar
2021-12-17 19:48           ` Adhemerval Zanella
2021-12-17 19:50             ` Siddhesh Poyarekar
2022-01-12  4:14   ` Siddhesh Poyarekar [this message]
2022-01-12 12:52     ` Adhemerval Zanella

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=4da0567f-deee-bd87-14d3-ece15aff5091@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).