Re: Rust front-end
Hi David We made a table to try and track this a bit better: | Patch | Reviewed | Accepted | |-+--+--| | 0001-Use-DW_ATE_UTF-for-the-Rust-char-type.patch| x | x| | 0002-gccrs-Add-nessecary-hooks-for-a-Rust-front-end-tests.patch | x | x| | 0003-gccrs-Add-Debug-info-testsuite.patch | | | | 0004-gccrs-Add-link-cases-testsuite.patch | | | | 0005-gccrs-Add-general-compilation-test-cases.patch | | | | 0006-gccrs-Add-execution-test-cases.patch | | | | 0007-gccrs-Add-gcc-check-target-check-rust.patch| x | | | 0008-gccrs-Add-the-Rust-front-end-AST-data-structures.patch | | | | 0009-gccrs-Add-Lexer-for-Rust-front-end.patch | x | | | 0010-gccrs-Add-Parser-for-Rust-front-end.patch | | | | 0011-gccrs-Add-expansion-pass-for-the-Rust-front-end.patch | | | | 0012-gccrs-Add-name-resolution-pass-to-the-Rust-front-end.patch | | | | 0013-gccrs-Add-second-intermedite-representation-called-H.patch | | | | 0014-gccrs-Add-AST-to-HIR-lowering-pass.patch | | | | 0015-gccrs-Add-wrapper-for-make_unique.patch| | | | 0016-gccrs-Add-port-of-FNV-hash-used-during-legacy-symbol.patch | | | | 0017-gccrs-Add-Rust-ABI-enum-helpers.patch | | | | 0018-gccrs-Add-Base62-implementation.patch | | | | 0019-gccrs-Add-implementation-of-Optional.patch | | | | 0020-gccrs-Add-attributes-checker.patch | | | | 0021-gccrs-Add-helpers-mappings-canonical-path-and-lang-i.patch | | | | 0022-gccrs-Add-type-resolution-and-trait-solving-pass.patch | | | | 0023-gccrs-Add-unsafe-checks-for-Rust.patch | | | | 0024-gccrs-Add-const-checker.patch | | | | 0025-gccrs-Add-privacy-checks.patch | | | | 0026-gccrs-Add-dead-code-scan-on-HIR.patch | | | | 0027-gccrs-Add-unused-variable-scan.patch | | | | 0028-gccrs-Add-metadata-ouptput-pass.patch | | | | 0029-gccrs-HIR-to-GCC-GENERIC-lowering.patch| | | | 0030-gccrs-These-are-wrappers-ported-from-reusing-gccgo.patch | | | | 0031-gccrs-Add-GCC-Rust-front-end-Make-lang.in.patch| x | | | 0032-gccrs-Add-config-lang.in.patch | x | x| | 0033-gccrs-add-lang-spec.h.patch| | | | 0034-gccrs-add-lang.opt.patch | x | | | 0035-gccrs-add-compiler-driver.patch| | | | 0036-gccrs-compiler-proper-interface-kicks-off-the-pipeli.patch | | | | 0037-gccrs-Add-README-CONTRIBUTING-and-compiler-logo.patch | | | I think the formatting from org-mode didn't come through 100%, but it looks readable enough. The patches which are reviewed but not accepted have issues which we have fixed locally in preparation for sending version 3 of the patches. I also found using this link made it much easier to see which patches have had reviews and which have not: https://inbox.sourceware.org/gcc-patches/20220824115956.737931-9-philip.her...@embecosm.com/T/#rbff0bb3df2780fecd9ee3d2baa864d9140d24b54 You can easily see the thread of patches and those which have responses and which have not. Thanks --Phil On Tue, 4 Oct 2022 at 13:43, David Malcolm wrote: > > On Tue, 2022-10-04 at 13:29 +0100, Philip Herron wrote: > > Hi everyone, > > > > As the cut-off for merging is coming up in November, quite a few of > > our patches have not been reviewed yet. > > > > There are a few main issues that have been raised so far, and we are > > fixing those at the moment in preparation for version 3 of the > > patches. Is there anything else we can do to make reviewing the rest > > of the patches easier? > > Do you have a list of which patches need reviewing? > e.g. perhaps a page showing: > - which patches are waiting for a reviewer, as opposed to > - which patches are already approved > - which patches have issues identified in review > - ...where no-one is yet working on addressing them > - ...where someone is working on addressing them > etc > > to make it clearer what the next action is for each patch, and who is > meant to be t
Re: Rust front-end
Hi Jakub, Thanks for this, as I mentioned in my response to David we have made a table and use this link to try and see what's going on https://inbox.sourceware.org/gcc-patches/20220824115956.737931-9-philip.her...@embecosm.com/T/#rbff0bb3df2780fecd9ee3d2baa864d9140d24b54 Do you think I should send a PING email to each patch which we are waiting on review for? Thanks --Phil On Tue, 4 Oct 2022 at 14:04, Jakub Jelinek wrote: > > On Tue, Oct 04, 2022 at 08:42:58AM -0400, David Malcolm via Gcc wrote: > > On Tue, 2022-10-04 at 13:29 +0100, Philip Herron wrote: > > > Hi everyone, > > > > > > As the cut-off for merging is coming up in November, quite a few of > > > our patches have not been reviewed yet. > > > > > > There are a few main issues that have been raised so far, and we are > > > fixing those at the moment in preparation for version 3 of the > > > patches. Is there anything else we can do to make reviewing the rest > > > of the patches easier? > > > > Do you have a list of which patches need reviewing? > > e.g. perhaps a page showing: > > - which patches are waiting for a reviewer, as opposed to > > - which patches are already approved > > - which patches have issues identified in review > > - ...where no-one is yet working on addressing them > > - ...where someone is working on addressing them > > etc > > > > to make it clearer what the next action is for each patch, and who is > > meant to be taking it. > > > > (within Red Hat, we used to call this "who has the ball?") > > Yeah, our policy in https://gcc.gnu.org/contribute.html states that > "Pinging patches, Getting patches applied > > If you do not receive a response to a patch that you have submitted within > two weeks or so, it may be a good idea to chase it by sending a follow-up > e-mail to the same list(s). Patches can occasionally fall through the > cracks. Please be sure to include a brief summary of the patch and the URL > of the entry in the mailing list archive of the original submission." > > If some patches have been already reviewed, others partly, others in the > works and others need review, sending a mail with those details > so that it is easy to find out what is still pending is appreciated even > more. > > Jakub >
[RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Oct 06, 2022)
Hi all, Here is the agenda for tomorrow's RISC-V GNU toolchain meeting. If you have any topics want to discuss or share, please let me know and I will add them to the agenda, thanks. Agenda: - RISC-V in GNU Cauldron - Common framework for register pairs: Z[dq]inx and P-extension - RISC-V sub-extension supports progress RVV gcc support progress Zmmul gcc support progress ZVFH extension support plan - Open discuss Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting. Topic: RISC-V GNU Toolchain Biweekly Sync-up Time: Oct 06, 2022 11:00 PM Singapore Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics Join Zoom Meeting https://zoom.us/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09 Meeting ID: 893 9360 0951 Passcode: 899662 BEIJING, China 11:00pThu, Oct 06 2022 12:00aFri, Oct 06 2022 PST/PDT, Pacific Standard Time (US) 8:00aThu, Oct 06 2022 9:00aThu, Oct 06 2022 PHILADELPHIA, United States, Pennsylvania 11:00aThu, Oct 06 2022 12:00aThu, Oct 06 2022 Paris, France 17:00pThu, Oct 06 2022 18:00pThu, Oct 06 2022BEGIN:VCALENDAR PRODID:-//zoom.us//iCalendar Event//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:PUBLISH CLASS:PUBLIC BEGIN:VTIMEZONE TZID:Asia/Singapore LAST-MODIFIED:20220317T223602Z TZURL:http://tzurl.org/zoneinfo-outlook/Asia/Singapore X-LIC-LOCATION:Asia/Singapore BEGIN:STANDARD TZNAME:+08 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 DTSTART:19700101T00 END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20220713T134316Z DTSTART;TZID=Asia/Singapore:20220714T23 DTEND;TZID=Asia/Singapore:20220715T00 SUMMARY:RISC-V GNU Toolchain Biweekly Sync-up RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20230323T16;INTERVAL=2;BYDAY=TH UID:ZOOM89393600951 TZID:Asia/Singapore DESCRIPTION:Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting .\n\nJoin Zoom Meeting\nhttps://us02web.zoom.us/j/89393600951?pwd=ZFpWMk Z6Tm1TbUFXT1hZZjZZMHhRQT09\n\nMeeting ID: 893 9360 0951\nPasscode: 89966 2\nOne tap mobile\n+6531651065\,\,89393600951#\,\,\,\,*899662# Singapore \n+6531587288\,\,89393600951#\,\,\,\,*899662# Singapore\n\nDial by your location\n+65 3165 1065 Singapore\n+65 3158 7288 Singapo re\n+1 669 900 9128 US (San Jose)\n+1 669 444 9171 US\n +1 346 248 7799 US (Houston)\n+1 253 215 8782 US (Tacoma) \n+1 312 626 6799 US (Chicago)\n+1 646 558 8656 US (New York)\n+1 646 931 3860 US\n+1 301 715 8592 US (Washingto n DC)\nMeeting ID: 893 9360 0951\nPasscode: 899662\nFind your local numb er: https://us02web.zoom.us/u/kk9cyIPNJ\n\n LOCATION:https://us02web.zoom.us/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZj ZZMHhRQT09 BEGIN:VALARM TRIGGER:-PT10M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR
GNU MPFR 4.1.1 Release Candidate
The release of GNU MPFR 4.1.1 ("épinards à la crème", patch level 1)
is imminent. Please help to make this release as good as possible
by downloading and testing this release candidate:
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.xz
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.bz2
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.gz
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.zip
The SHA1 digests:
1a01a100d91f91760f116c1f3efb77fc87ebab28 mpfr-4.1.1-rc1.tar.bz2
f8097f9cdd10312a9b554012aec3230bdc719a17 mpfr-4.1.1-rc1.tar.gz
903d59de1b6e08b8570f3673080f8e2a1129c94c mpfr-4.1.1-rc1.tar.xz
a371751f71cef3874c91fdc81b4d41bd61dd0311 mpfr-4.1.1-rc1.zip
The SHA256 digests:
0da78120b10d2f51265fc7da2786f5a8cea960ae2e91e55865a0e7b2a5ab56e4
mpfr-4.1.1-rc1.tar.bz2
ecb2045d9cab07290c02a5a70a37f0be822f679b3ba276628e2a6ba08cf97295
mpfr-4.1.1-rc1.tar.gz
7b78560f8101825fde2ff22cda292917f022c862232da71062307f015f0b3942
mpfr-4.1.1-rc1.tar.xz
d932a61386e2d1e69a1445f6f6794c19e42c6751c3c34845183c408b277a6e21
mpfr-4.1.1-rc1.zip
The signatures:
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.xz.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.bz2.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.gz.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.zip.asc
Each tarball is signed by Vincent Lefèvre. This can be verified using
the GPG key ID 5831D11A0D4DB02A; this key can be retrieved with:
gpg --recv-keys 5831D11A0D4DB02A
or by downloading it from .
The key fingerprint is:
A534 BE3F 83E2 41D9 1828 0AEB 5831 D11A 0D4D B02A
The signatures can be verified with: gpg --verify
You should check that the key fingerprint matches.
Changes from version 4.1.0 to version 4.1.1:
- Bug fixes (see and/or the
ChangeLog file), in particular for macros implementing functions.
- Improved manual formatting, by using a recent texinfo.tex file.
Please send success and failure reports with "./config.guess" output
to .
If no problems are found, GNU MPFR 4.1.1 should be released
around 2022-10-15.
Note: InriaForge closed last year, so some URLs on the MPFR website
(those at gforge.inria.fr) no longer work. I have converted the links
to commits, as those at .
I'll try to do additional changes in the next few days.
Regards,
--
Vincent Lefèvre - Web:
