GCC 12.5 Release Candidate available from gcc.gnu.org

2025-07-04 Thread Richard Biener via Gcc
The first release candidate for GCC 12.5 is available from

 https://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
 ftp://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/

and shortly its mirrors.  It has been generated from git commit
r12-11250-gb71ac987cd1499.

I have so far bootstrapped and tested the release candidate on
x86_64-linux.
Please test it and report any issues to bugzilla.

If all goes well, we'd like to release 12.5 on Friday, Jul 11th
and close the branch.


GCC 12.4.1 Status Report (2025-07-04), branch frozen for release

2025-07-04 Thread Richard Biener via Gcc
Status
==

The gcc-12 branch is now frozen for release and closing of
the branch.


Quality Data


Priority  #   Change from last report
---   ---
P10
P2  572   -  44
P3  112
P4  192
P5   22
---   ---
Total P1-P3 684   -  44
Total   898   -  44


Previous Report
===

https://gcc.gnu.org/pipermail/gcc/2025-June/246136.html


Re: What's up with CXXFLAGS_FOR_BUILD?

2025-07-04 Thread Eric Botcazou
> This raises two, presumably related, questions.
> 
> 1) What is CXXFLAGS_FOR_BUILD supposed to be doing?

Set CXXFLAGS when you're compiling something for the build platform.

> 2) How can I set compilation switches for gcc stuff (like the gcc/cobol
> front end) without affecting lib*** stuff?

In this case you're compiling something for the host platform and CXXFLAGS is 
the appropriate variable.

You need to pass the various FLAGS on the 'make' command line instead of the 
'configure' command line.

-- 
Eric Botcazou




Re: Criteria for adding AIX as a secondary platform.

2025-07-04 Thread swamy sangamesh via Gcc
Tried with the below change and able to bootstrap on AIX and X86.

diff --git a/gcc/tree.cc b/gcc/tree.cc
index e9a83e4260b..b693a58ab9d 100644
--- a/gcc/tree.cc
+++ b/gcc/tree.cc
@@ -64,6 +64,7 @@ along with GCC; see the file COPYING3.  If not see
 #include "stringpool.h"
 #include "attribs.h"
 #include "rtl.h"
+#include "tm_p.h"
 #include "regs.h"
 #include "tree-vector-builder.h"
 #include "gimple-fold.h"

Please suggest if this is the right place to add tm_p.h.


On Tue, Jul 1, 2025 at 11:04 PM Andrew Pinski  wrote:

> On Tue, Jul 1, 2025 at 10:31 AM swamy sangamesh via Gcc 
> wrote:
> >
> > Thank you all for your response.
> >
> > I would be posting regression test results regularly and will work on
> > setting up a buildbot for AIX.
> >
> > I can see that currently the AIX build is broken with the below error.
> >
> > In file included from ./tm.h:25,
> >  from
> /opt/freeware/src/packages/BUILD/gcc/gcc/backend.h:28,
> >  from
> /opt/freeware/src/packages/BUILD/gcc/gcc/tree.cc:33:
> > /opt/freeware/src/packages/BUILD/gcc/gcc/tree.cc: In function 'tree_node*
> > generate_internal_label(const char*)':
> > /opt/freeware/src/packages/BUILD/gcc/gcc/config/rs6000/xcoff.h:206:30:
> > error: 'rs6000_xcoff_strip_dollar' was not declared in this scope
> >   206 |   sprintf (LABEL, "*%s..%u", rs6000_xcoff_strip_dollar (PREFIX),
> > (unsigned) (NUM))
> >   |  ^
> > /opt/freeware/src/packages/BUILD/gcc/gcc/tree.cc:819:3: note: in
> expansion
> > of macro 'ASM_GENERATE_INTERNAL_LABEL'
> >   819 |   ASM_GENERATE_INTERNAL_LABEL (tmp, prefix, num++);
> >
> > This seems to have caused by
> >
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=0337e3c2743ca0c57da8c6b78b725a7d83f0b721
> >
> > Analysing more on this failure.
>
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120866#c4 explictly .
>
> Thanks,
> Andrew
>
>
> >
> > Thanks,
> > Sangamesh
> >
> > On Mon, Jun 30, 2025 at 8:48 PM David Edelsohn 
> wrote:
> >
> > > The general criteria for primary, secondary, and tertiary platforms are
> > > described on the page to which you linked.
> > >
> > > The choice of level is decided by the GCC Steering Committee in
> > > consultation with the GCC Release Managers and the maintainers for the
> > > targets / platforms.
> > >
> > > AIX is an unusual platform that always has required extra effort from
> the
> > > GCC community.  The reduction in participation and investment from IBM
> > > means that the GCC community cannot tie its functional status to the
> > > release criteria for GCC.
> > >
> > > Thanks, David
> > >
> > > On Mon, Jun 30, 2025 at 10:48 AM swamy sangamesh <
> > > swamy.sangam...@gmail.com> wrote:
> > >
> > >> Hi All,
> > >>
> > >> Would like to know the criteria for adding AIX as a secondary
> platform.
> > >> https://gcc.gnu.org/gcc-15/criteria.html
> > >>
> > >> Willing to participate in the work needed for the platform to be
> added as
> > >> primary and secondary.
> > >>
> > >>
> > >> --
> > >> Thanks & Regards,
> > >> Sangamesh
> > >>
> > >
> >
> > --
> > Thanks & Regards,
> > Sangamesh
>


-- 
Thanks & Regards,
Sangamesh


RE: What's up with CXXFLAGS_FOR_BUILD?

2025-07-04 Thread Robert Dubner


> -Original Message-
> From: Eric Botcazou 
> Sent: Friday, July 4, 2025 04:11
> To: Robert Dubner 
> Cc: gcc@gcc.gnu.org
> Subject: Re: What's up with CXXFLAGS_FOR_BUILD?
> 
> > This raises two, presumably related, questions.
> >
> > 1) What is CXXFLAGS_FOR_BUILD supposed to be doing?
> 
> Set CXXFLAGS when you're compiling something for the build platform.
> 
> > 2) How can I set compilation switches for gcc stuff (like the
gcc/cobol
> > front end) without affecting lib*** stuff?
> 
> In this case you're compiling something for the host platform and
CXXFLAGS
> is
> the appropriate variable.

And therein lies the rub.

With the COBOL front end, we recently hit a situation where we
inadvertently used a C++17 feature that resulted in a compilation failure
using GCC-9.

So, I want to be able to set "-std=c++14" when compiling the COBOL front
end.

But when I set CXXFLAGS="-std=c++14", that causes the compilation of
libcody to fail.  It insists on the standard being exactly C++11.

I suppose the proper question is, "How do I set compilation flags for just
the gcc/cobol front end compilation?"

Best regards, and thanks very much for getting back to me on this...

Bob Dubner


> 
> You need to pass the various FLAGS on the 'make' command line instead of
> the
> 'configure' command line.
> 
> --
> Eric Botcazou
> 



gcc-14-20250704 is now available

2025-07-04 Thread GCC Administrator via Gcc
Snapshot gcc-14-20250704 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/14-20250704/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-14 revision e086e745a245e482d3c330c9b1d4ca929e01a220

You'll find:

 gcc-14-20250704.tar.xz   Complete GCC

  SHA256=c6a158d3add7d36a992c6bdf367cbb95673cc4ba7728eb61ad1808ed8792415a
  SHA1=08b999d817523fd93918f74c8ae799146e615762

Diffs from 14-20250627 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-14
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.


Compiler optimization help

2025-07-04 Thread Thomas de Bock via Gcc
Hello, I'm looking to contribute to the project, hoping to implement the 
compiler optimization specified in: 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63164. Would appreciate any 
help/tips regarding what files I should look at to start working towards 
implementing something like this, cheers!

This e-mail and any attachments may contain information that is confidential 
and proprietary and otherwise protected from disclosure. If you are not the 
intended recipient of this e-mail, do not read, duplicate or redistribute it by 
any means. Please immediately delete it and any attachments and notify the 
sender that you have received it by mistake. Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail or any 
attachments. The DRW Companies make no representations that this e-mail or any 
attachments are free of computer viruses or other defects.