Re: More C type errors by default for GCC 14

On 5/15/23, Richard Earnshaw (lists) via Gcc wrote: > On 10/05/2023 03:38, Eli Zaretskii via Gcc wrote: >>> From: Arsen Arsenović >>> Cc: Eli Zaretskii , Jakub Jelinek , >>> jwakely@gmail.com, gcc@gcc.gnu.org >>> Date: Tue, 09 May 2023 22:21:03 +0200 >>> The concern is using the good w

Re: [wish] Flexible array members in unions

> On May 12, 2023, at 2:16 AM, Richard Biener via Gcc wrote: > > On Thu, May 11, 2023 at 11:14 PM Kees Cook via Gcc wrote: >> >> On Thu, May 11, 2023 at 08:53:52PM +, Joseph Myers wrote: >>> On Thu, 11 May 2023, Kees Cook via Gcc wrote: >>> On Thu, May 11, 2023 at 06:29:10PM +0200,

Sourceware joins Software Freedom Conservancy

https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/ After various discussions and lots of positive feedback [1] [2] [3] [4] Software Freedom Conservancy and Sourceware proudly announce that Sourceware today joins SFC as a member project! As the fiscal host of Sourceware, Software Fre

Re: For GCC, newlib combined tree, newlib build-tree testing, use standard search paths

Sounds fine Thomas. Thanks. -- Jeff J. On Mon, May 15, 2023 at 4:01 AM Thomas Schwinge wrote: > Hi! > > On 2023-05-08T21:50:56+0200, I wrote: > > Ping: OK to push to newlib main branch the attached > > "For GCC, newlib combined tree, newlib build-tree testing, use standard > search paths"? > >

Re: More C type errors by default for GCC 14

On 12/05/2023 13:30, Jakub Jelinek via Gcc wrote: On Fri, May 12, 2023 at 11:33:01AM +0200, Martin Jambor wrote: One fairly big GCC-internal task is to clear up the C test suite so that it passes with the new compiler defaults. I already have an offer of help for that, so I think we can complet

Re: More C type errors by default for GCC 14

Hello, On Fri, 12 May 2023, Florian Weimer wrote: > * Alexander Monakov: > > > This is not valid (constraint violation): > > > > unsigned x; > > > > int *p = &x; > > > > In GCC this is diagnosed under -Wpointer-sign: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25892 > > Thanks fo

Re: More C type errors by default for GCC 14

Hello, On Fri, 12 May 2023, Jakub Jelinek via Gcc wrote: > On Fri, May 12, 2023 at 11:33:01AM +0200, Martin Jambor wrote: > > > One fairly big GCC-internal task is to clear up the C test suite so that > > > it passes with the new compiler defaults. I already have an offer of > > > help for that,

Re: More C type errors by default for GCC 14

On 10/05/2023 03:38, Eli Zaretskii via Gcc wrote: From: Arsen Arsenović Cc: Eli Zaretskii , Jakub Jelinek , jwakely@gmail.com, gcc@gcc.gnu.org Date: Tue, 09 May 2023 22:21:03 +0200 The concern is using the good will of the GNU Toolchain brand as the tip of the spear or battering ram to m

RISC-V V C Intrinsic API v1.0 release meeting reminder (May 15th, 2023)

Hi all, A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic API v1.0 is going to be held later on 2023/05/15 7AM (GMT -7) / 10PM (GMT +8). The agenda can be found in the second page of the meeting slides (link

GCC 11.3.1 Status Report (2023-05-15)

Status == The gcc-11 branch is open for regression and documentation fixes. It's time to do the annual release from the branch, GCC 12.4. I'd like to make the first release candidate on Monday, May 22nd, and a release one week later if all goes well. Please look through bugzilla and see whic

Re: For GCC, newlib combined tree, newlib build-tree testing, use standard search paths

Hi! On 2023-05-08T21:50:56+0200, I wrote: > Ping: OK to push to newlib main branch the attached > "For GCC, newlib combined tree, newlib build-tree testing, use standard > search paths"? > Or, has anybody got adverse comments/insight into this? Given that nobody has any comments, I'll push this