GCC 9.4 Status Report (2021-05-19), branch frozen for release
Status == The GCC 9 branch is now frozen for the upcoming GCC 9.4 release. I will announce a first release candidate shortly. All changes require release manager approval now. Quality Data Priority # Change from last report --- --- P1- 1 P2 304 - 7 P3 23 + 7 P4 174 P5 23 --- --- Total P1-P3 328 - 1 Total 525 - 1 Previous Report === https://gcc.gnu.org/pipermail/gcc/2021-April/235948.html
GCC 9.4 Release Candidate available
The first release candidate for GCC 9.4 is available from
https://sourceware.org/pub/gcc/snapshots/9.4.0-RC-20210519/
and shortly its mirrors. It has been generated from git commit
8091c46cf736124a106922ddfd1fdb99f33b0241.
I have so far bootstrapped and tested the release candidate
on {x86_64,i586,aarch64,ppc64le,s390x,riscv64,ppc,ppc64,armv7l}-linux.
Please test it and report any issues to bugzilla.
If all goes well I'd like to release 9.4 on Friday, June 28th.
Re: GCC 9.4 Release Candidate available
On Wed, 19 May 2021, Richard Biener wrote:
>
> The first release candidate for GCC 9.4 is available from
>
> https://sourceware.org/pub/gcc/snapshots/9.4.0-RC-20210519/
>
> and shortly its mirrors. It has been generated from git commit
> 8091c46cf736124a106922ddfd1fdb99f33b0241.
>
> I have so far bootstrapped and tested the release candidate
> on {x86_64,i586,aarch64,ppc64le,s390x,riscv64,ppc,ppc64,armv7l}-linux.
>
> Please test it and report any issues to bugzilla.
>
> If all goes well I'd like to release 9.4 on Friday, June 28th.
May 28th, of course.
Richard.
How to skip dg-module-cmi?
Hi Nathan: Recently I am clean up the failed case for bare-matel riscv64 target, and that not support omp due to lack of pthread support (e.g. gcc/testsuite/g++.dg/modules/omp-1_a), however even I add `dg-require-effective-target pthread`, `dg-module-cmi` seems still try to test and then get failed. So is there a right way to skip `dg-module-cmi` testing? Thanks :)
[RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (May 20, 2021)
Hi all, There is an agenda for tomorrow's meeting. If you have topics to discuss or share, please let me know and I can add them to the agenda. ## Agenda: 1. Document ELF attribute section https://github.com/riscv/riscv-elf-psabi-doc/pull/71 2. Calling conventions for the lazily bound functions. #190 https://github.com/riscv/riscv-elf-psabi-doc/pull/190 3. Built-in function naming scheme https://github.com/riscv/riscv-c-api-doc/issues/19 4. The status of P,K,B,Zfinx,Zce extension developing in GCC part 5. The CI/Testing infrastructure for RISC-V 6. Free Discussion https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics BEIJING, China 11:00pThu, May 20 2021 12:00aFri, May 21 2021 PDT/PST, Pacific Daylight Time (US) 8:00aThu, May 20 2021 9:00aThu, May 20 2021 LONDON, United Kingdom, England 4:00pThu, May 20 2021 5:00pThu, May 20 2021 Join Zoom Meeting https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09 Meeting ID: 893 9360 0951 Passcode: 899662 -- Best wishes, Wei Wu (吴伟)
Freenode changing ownership
Recently I have noticed a post going around various FOSS circles about Freenode changing hands: https://gist.github.com/joepie91/df80d8d36cd9d1bde46ba018af497409 I also checked the GCC wiki, and on both its main page and its GCConIRC page it advertises an IRC channel on Freenode for GCC: https://gcc.gnu.org/wiki and https://gcc.gnu.org/wiki/GCConIRC Many other projects have been talking about moving their IRC channels to other servers in wake of this ownership change; is GCC going to do likewise? Since GCC already also has an IRC channel on OFTC, maybe the Freenode one could be moved there as well? Of course, that would require coming up with a new name for the one being migrated from Freenode, so that it doesn't clash with the existing GCC channel on OFTC... Anyways, just something to consider; let me know if the community decides anything. Thanks, Eric Gallager
Re: Freenode changing ownership
>Of course, that would require coming up with a new name for the one >being migrated from Freenode, so that it doesn't clash with the >existing GCC channel on OFTC For consistency with the mailing lists, #gcc-help seems like an obvious choice (if we do want to move it to OFTC rather than libera.chat).
