> On May 7, 2024, at 17:52, Kees Cook wrote:
>
> On Tue, May 07, 2024 at 06:34:19PM +, Qing Zhao wrote:
>> On May 7, 2024, at 13:57, Sebastian Huber
>> wrote:
>>> On 07.05.24 16:26, Qing Zhao wrote:
Hi, Sebastian,
Thanks for your explanation.
Our goal is to deprecate the
On Tue, 7 May 2024, Kees Cook wrote:
> On Tue, May 07, 2024 at 06:34:19PM +, Qing Zhao wrote:
> > On May 7, 2024, at 13:57, Sebastian Huber
> > wrote:
> > > On 07.05.24 16:26, Qing Zhao wrote:
> > > > Hi, Sebastian,
> > > > Thanks for your explanation.
> > > > Our goal is to deprecate the
On Tue, May 07, 2024 at 06:34:19PM +, Qing Zhao wrote:
> On May 7, 2024, at 13:57, Sebastian Huber
> wrote:
> > On 07.05.24 16:26, Qing Zhao wrote:
> > > Hi, Sebastian,
> > > Thanks for your explanation.
> > > Our goal is to deprecate the GCC extension on structure
> > > containing a
(Resend since my previous email in HTML and inline quoting wasn’t work, I
changed the mail setting, hopefully this time it’s good). Sorry for the
inconvenience.
> On May 7, 2024, at 13:57, Sebastian Huber
> wrote:
>
> On 07.05.24 16:26, Qing Zhao wrote:
>> Hi, Sebastian,
>> Thanks for your
On May 7, 2024, at 13:57, Sebastian Huber
wrote:
On 07.05.24 16:26, Qing Zhao wrote:
Hi, Sebastian,
Thanks for your explanation.
Our goal is to deprecate the GCC extension on structure containing a flexible
array member not at the end of another structure. In order to achieve this
goal, we
On 07.05.24 16:26, Qing Zhao wrote:
Hi, Sebastian,
Thanks for your explanation.
Our goal is to deprecate the GCC extension on structure containing a flexible
array member not at the end of another structure. In order to achieve this
goal, we provided the warning option
Hi, Sebastian,
Thanks for your explanation.
Our goal is to deprecate the GCC extension on structure containing a flexible
array member not at the end of another structure. In order to achieve this
goal, we provided the warning option -Wflex-array-member-not-at-end for the
users to
locate all
On 06.05.24 16:20, Qing Zhao wrote:
Hi, Sebastian,
Looks like that the behavior you described is correct.
What’s your major concern? ( a little confused).
I am concerned that the static initialization of structures with
flexible array members no longer works. In the RTEMS open source
Hi, Sebastian,
Looks like that the behavior you described is correct.
What’s your major concern? ( a little confused).
Qing
On May 6, 2024, at 09:29, Sebastian Huber
wrote:
On 06.05.24 09:08, Richard Biener wrote:
On Sat, 4 May 2024, Sebastian Huber wrote:
On 07.08.23 16:22, Qing Zhao via
On 06.05.24 09:08, Richard Biener wrote:
On Sat, 4 May 2024, Sebastian Huber wrote:
On 07.08.23 16:22, Qing Zhao via Gcc-patches wrote:
Hi,
This is the 2nd version of the patch.
Comparing to the 1st version, the only change is to address Richard's
comment on refering a warning option for
On Sat, 4 May 2024, Sebastian Huber wrote:
> On 07.08.23 16:22, Qing Zhao via Gcc-patches wrote:
> > Hi,
> >
> > This is the 2nd version of the patch.
> > Comparing to the 1st version, the only change is to address Richard's
> > comment on refering a warning option for diagnosing deprecated
On 07.08.23 16:22, Qing Zhao via Gcc-patches wrote:
Hi,
This is the 2nd version of the patch.
Comparing to the 1st version, the only change is to address Richard's
comment on refering a warning option for diagnosing deprecated behavior.
Okay for committing?
thanks.
Qing
==
On Thu, Oct 19, 2023 at 08:49:00PM +, Qing Zhao wrote:
> > On Sep 25, 2023, at 2:24 PM, Tobias Burnus wrote:
> > Secondly, if this is deprecated, shouldn't then the warning enabled by,
> > e.g., -Wall or made
> > otherwise more prominent? (-std=?) - Currently, one either has to find the
> >
Hi, Tobias,
Sorry for the late reply (just came back from a long vacation after Cauldron).
And thank you for reporting this issue.
Please see my reply embedded below:
> On Sep 25, 2023, at 2:24 PM, Tobias Burnus wrote:
>
> Hi all,
>
> I stumbled over this as I found the wording in the
Hi, Tobias,
Sorry for the late reply.
I has been on vacation after Cauldron, and will be back to work in the mid of
Oct. will look at this issue at that time.
Qing
> On Sep 25, 2023, at 2:24 PM, Tobias Burnus wrote:
>
> Hi all,
>
> I stumbled over this as I found the wording in the release
On Mon, 25 Sep 2023, Tobias Burnus wrote:
> Hi all,
>
> I stumbled over this as I found the wording in the release notes rather
> unclear.is.
>
>
> First, the following gives only a -pedantic warning and not a
> -Wflex-array-member-not-at-end:
>
> struct t { int b; int x[]; };
> struct q
Hi all,
I stumbled over this as I found the wording in the release notes rather
unclear.is.
First, the following gives only a -pedantic warning and not a
-Wflex-array-member-not-at-end:
struct t { int b; int x[]; };
struct q { int b; struct t a[2]; int c; };
warning: invalid use of
On Mon, 7 Aug 2023, Qing Zhao wrote:
> Hi,
>
> This is the 2nd version of the patch.
> Comparing to the 1st version, the only change is to address Richard's
> comment on refering a warning option for diagnosing deprecated behavior.
>
>
> Okay for committing?
OK.
> thanks.
>
> Qing
>
>
Hi,
This is the 2nd version of the patch.
Comparing to the 1st version, the only change is to address Richard's
comment on refering a warning option for diagnosing deprecated behavior.
Okay for committing?
thanks.
Qing
==
*htdocs/gcc-14/changes.html (Caveats): Add notice about
19 matches
Mail list logo
