From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Cristian Rodríguez" <cristian@rodriguez.im>, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/6] Support use of -fstrict-flex-arrays in user code
Date: Wed, 19 Jul 2023 11:27:50 -0300 [thread overview]
Message-ID: <8f7899a4-0816-2581-55df-346bf69d93a3@linaro.org> (raw)
In-Reply-To: <CAPBLoAfKppR3bxRHCKHoyUxa_AEH_sTNa7Lhas0p9esCQcW+ZQ@mail.gmail.com>
On 19/07/23 09:40, Cristian Rodríguez via Libc-alpha wrote:
> On Mon, Jul 10, 2023 at 11:05 AM Cristian Rodríguez <cristian@rodriguez.im>
> wrote:
>
>> Currently GCC 13 -fstrict-flex-arrays cannot be used safely with user
>> code because the library makes use of pre-c99 flexible arrays.
>>
>> This series introduces a macro to annotate such uses and grandfathers-in
>> this legacy use.
>>
>> This series only cover the user-visible *library* types. the linux kernel
>> types
>> are subject to a different patch set and discussion since the kernel has
>> moved on to c11 leaving pre-c99 compatibilty behind.
>>
>>
>>
>>
> Any comments about this series.. ? as is it should introduce no
> regressions.
Can't we use the already define __flexarr/__glibc_c99_flexarr_available macro
instead? Or do we really need to handle the usage of -fstrict-flex-arrays
with pre-c99 usage?
next prev parent reply other threads:[~2023-07-19 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:04 Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 1/6] Introduce __decl_is_flex_array macro Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 2/6] dlfcn : annotate dls_serpath with __decl_is_flex_array Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 3/6] inet: annotate tu_data and tu_stuff " Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 4/6] inet: annotate ip6r0_addr " Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 5/6] io: annotate fts_name " Cristian Rodríguez
2023-07-10 15:04 ` [PATCH 6/6] misc: annotate q_data " Cristian Rodríguez
2023-07-19 12:40 ` [PATCH 0/6] Support use of -fstrict-flex-arrays in user code Cristian Rodríguez
2023-07-19 14:27 ` Adhemerval Zanella Netto [this message]
2023-07-19 14:57 ` Cristian Rodríguez
2023-07-19 17:48 ` Adhemerval Zanella Netto
2023-08-11 15:34 ` Cristian Rodríguez
2023-08-11 22:10 ` Paul Eggert
2023-08-12 11:07 ` Alejandro Colomar
2023-08-12 13:29 ` Alejandro Colomar
2023-08-12 14:53 ` Cristian Rodríguez
2023-08-12 18:20 ` Paul Eggert
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=8f7899a4-0816-2581-55df-346bf69d93a3@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=cristian@rodriguez.im \
--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).