Okay, thanks all for the comments and suggestions.
Based on the discussion so far, I have the following plan for resolving this
issue:
In GCC13:
1. Add documentation in extend.texi to include all the following 3 cases as GCC
extension:
Case 1: The structure with a flexible array member is the
On Thu, 2 Feb 2023, Siddhesh Poyarekar wrote:
> I dug into this on the glibc end and it looks like this commit:
>
> commit 63fb8f9aa9d19f85599afe4b849b567aefd70a36
> Author: Zack Weinberg
> Date: Mon Feb 5 14:13:41 2018 -0500
>
> Post-cleanup 2: minimize _G_config.h.
>
> ripped all of th
On 2/2/23 10:05, Kees Cook via Gcc-patches wrote:
Right -- this can lead (at least) to type confusion and other problems
too. We've been trying to remove all of these overlaps in the Linux
kernel. I mention it the "Overlapping composite structure members"
section at https://people.kernel.org
> On Feb 2, 2023, at 11:25 PM, Siddhesh Poyarekar wrote:
>
> On 2023-02-02 03:33, Richard Biener wrote:
>> looking at PR77650 what seems missing there is the semantics of this
>> extension as expected/required by the glibc use. comment#5 seems
>> to suggest that for my example above its expec
On 2023-02-02 03:33, Richard Biener wrote:
looking at PR77650 what seems missing there is the semantics of this
extension as expected/required by the glibc use. comment#5 seems
to suggest that for my example above its expected that
Y.x.data[0] aliases Y.end?! There must be a better way to write
On Thu, Feb 02, 2023 at 02:31:53PM +, Qing Zhao wrote:
>
> > On Feb 2, 2023, at 3:33 AM, Richard Biener wrote:
> >
> > On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
> >
> >> On 2023-02-01 13:24, Qing Zhao wrote:
> >>>
> >>>
> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
> wr
> On Feb 2, 2023, at 3:33 AM, Richard Biener wrote:
>
> On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
>
>> On 2023-02-01 13:24, Qing Zhao wrote:
>>>
>>>
On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
wrote:
On 2023-01-31 09:11, Qing Zhao wrote:
> Update documentati
On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
> On 2023-02-01 13:24, Qing Zhao wrote:
> >
> >
> >> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
> >> wrote:
> >>
> >> On 2023-01-31 09:11, Qing Zhao wrote:
> >>> Update documentation to clarify a GCC extension on structure with
> >>> flexible a
> On Feb 1, 2023, at 1:57 PM, Siddhesh Poyarekar wrote:
>
> On 2023-02-01 13:24, Qing Zhao wrote:
>>> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
>>>
>>> On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible arra
On 2023-02-01 13:24, Qing Zhao wrote:
On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible array member being nested in another structure.
gcc/ChangeLog:
* doc/extend.t
> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
>
> On 2023-01-31 09:11, Qing Zhao wrote:
>> Update documentation to clarify a GCC extension on structure with
>> flexible array member being nested in another structure.
>> gcc/ChangeLog:
>> * doc/extend.texi: Document GCC extensio
On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible array member being nested in another structure.
gcc/ChangeLog:
* doc/extend.texi: Document GCC extension on a structure containing
a flexible array member to be a mem
Update documentation to clarify a GCC extension on structure with
flexible array member being nested in another structure.
gcc/ChangeLog:
* doc/extend.texi: Document GCC extension on a structure containing
a flexible array member to be a member of another structure.
---
gcc/doc/e
13 matches
Mail list logo
