Re: Build failure due to format-truncation
On 18/06/21 00:05, Martin Sebor wrote: Right, with -O0 we understand why it happens. I think I have found a minimal way to reproduce the build failure: make BOOT_CFLAGS="-O0" bootstrap No environment variables set. Setting CFLAGS, CXXFLAGS or both does not seem to have any effect. Additionally at -O1 I found: ../../gcc-xtra/gcc/gimplify.c: In function ‘gimplify_status gimplify_omp_loop(tree_node**, gimple**)’: ../../gcc-xtra/gcc/gimplify.c:12975:17: error: ‘last’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 12975 | if (pass != last) | ^~ cc1plus: all warnings being treated as errors And finally at -O2 there were no problems. It would have been interesting to try other options, but the build takes an enormous amount of time... Thank you very much. Best regards, José Rui
gcc-12-20210620 is now available
Snapshot gcc-12-20210620 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20210620/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch master revision 69d80f0f2f0bb8a88cd82d8ab6c4b92cf8013ca1 You'll find: gcc-12-20210620.tar.xz Complete GCC SHA256=22ad84f536ea8812361606ff61a67e712915d3915e87252dfb30766eaa00a13e SHA1=ede25c889690069452f09b656179531c31a2ba26 Diffs from 12-20210613 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-12 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.
Hongtao Liu as x86 vectorization maintainer
I am pleased to announce that the GCC Steering Committee has appointed Hongtao Liu as maintainer of the i386 vector extensions in GCC. Hongtao, please update your listing in the MAINTAINERS file. Cheers, Jason
RE: Hongtao Liu as x86 vectorization maintainer
>-Original Message- >From: Jason Merrill >Sent: Monday, June 21, 2021 10:07 AM >To: Liu, Hongtao >Cc: gcc Mailing List ; Marek Polacek >Subject: Hongtao Liu as x86 vectorization maintainer > >I am pleased to announce that the GCC Steering Committee has appointed >Hongtao Liu as maintainer of the i386 vector extensions in GCC. > >Hongtao, please update your listing in the MAINTAINERS file. Updated, thanks. > >Cheers, >Jason
Looking for newcomer project
Hi all, I am want to contribute to GCC as a volunteer. And I am seeking the guidance on which project to select. I have build the GCC and run the test cases. I have read through GCC summer of code page and few other related documentation Currently I have no preference, I am available to any project that have good priority and guidance available.. I studied computer science in bachelor's course batch 2016-20, didn't completed though. I have some knowledge of LLVM but not at code implementation level. Definitely I am still a beginner in C/C++ to contribute such a large project GCC but I am enthusiastic to gain knowledge in the compiler development so can enhance it. Would be happy to be a part of GCC community and gain some knowledge. Thanks, Shivam
Re: [Patch] contrib/mklog.py: Improve PR handling (was: git gcc-commit-mklog doesn't extract PR number to ChangeLog)
On 18.06.21 16:41, Jason Merrill wrote: * Being able to specify the PR numbers on the command line in addition (currently, they are only extracted from the testsuite patches) This bit seems unnecessary to me, since we want the commit to include tests that identify the PR. I full hearty disagree! Martin Sebor's patch to extract the PR number from the testcase filename, as an alternative to a comment, should be enough. Regarding the PR from the filename, are we only talking about new files – or about modifications to old files? For new files, together with -p it seems to be useful; for old files, I think there will be more spurious/false PRs than useful/right PRs. Looking through the last few commits, in all of the following cases the -b would be useful — and I do regard the commits messages are sensible: * cc9c94d43dcfa98436152af9c00f011e9dab25f6 PR libstdc++/100387 added testsuite/25_algorithms/minmax/constrained.cc (etc.) but file neither has a pr... name nor contains a PR line (BTW: The fix is not primarily for the PR but fixes it as, a side effect; hence, not having a PR line makes sense) * 870b674f72d4894b94efa61764fd87ecec29ffde 'ranger' - removes a datastructure (no testcase but also does not make sense here) * 17a4bee01c3b29c5ccdd39f34384521e5d44135b Fixes an ICE for one testcase (but of course does not add a new testcase or modify an existing one.) * 76e990fd211cbb20bf74ce074eb8b2d7b096d3b7 fix a bootstrap issue (found with the GCC 11 backport). Those are all commits between last Friday and today. Hence, I do believe it makes sense to be able to specify the PR on the command line — besides obtaining it from file names. Tobias - Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf
