☠ Buildbot (GNU Toolchain): gccrust - failed compile (failure) (master)
A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/107/builds/8 Build state: failed compile (failure) Revision: 40ad6b290af7d4e2e4d4a35a759d1b21d60423f5 Worker: bb3 Build Reason: (unknown) Blamelist: Sebastien Lacoste , bors[bot] <26634292+bors[bot]@users.noreply.github.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/8/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/8/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/8/steps/3/logs/stdio - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/8/steps/4/logs/stdio - warnings (14): https://builder.sourceware.org/buildbot/#builders/107/builds/8/steps/4/logs/warnings__14_ -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Rust front-end
Hi everyone, Since November 2020, I've worked full-time on the Rust front-end for GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I am writing to this mailing list to seek feedback from the collective experience here early to plan a path for upstreaming the front-end into GCC. 1. What is the actual process of merging a prominent feature like this upstream - How do we review this? - Do we create a "mega-commit" patch - How long should we expect this review process to take - Is there anything we can do to make this easier? 2. What sort of quality does the GCC community expect? - I think it is essential that we can compile valid test cases from a testsuite and real projects before merging. - It seems reasonable that our error handling may not be 100% but be expected to improve over time - Upon merging, can features like Rust be marked as experimental 3. How do GCC releases work? - If you miss a window can we still merge code into the front-end? - Can we merge without a borrow checker and backport this in the future? 4. What about the possibility of merging sooner rather than later, which would help the project gain interest through the increased visibility of it as part of the GCC family. - Does this still allow for development churn, or will it cause friction? 5. Does anyone have prior experience or advice they could give us? For some context, my current project plan brings us to November 2022 where we (unexpected events permitting) should be able to support valid Rust code targeting Rustc version ~1.40 and reuse libcore, liballoc and libstd. This date does not account for the borrow checker feature and the proc macro crate, which we have a plan to implement, but this will be a further six-month project. Regarding patch management, we currently do our development on GitHub: https://github.com/Rust-GCC/gccrs; this means we can integrate our issue tracking with the official Rust project by linking back to the official Rust project's RFC issues, for example. The downside is that when someone uses our compiler and hits an ICE, they will be directed to the GCC Bugzilla, which is correct but can lead to a mismatch in issue tracking. Nevertheless, I think it's essential to have the GitHub link here to integrate with the broader Rust community. I believe we can triage Rust issues on the Bugzilla and raise associated ones on Github to manage this. From my perspective as the lead on this front-end, we are currently under heavy development, so this means a fair amount of code churn still, and I don't see this changing until we can successfully compile the libcore crate later this year. Although I would love to see us merged into GCC 13, I want to make sure this project is a success for everyone, and this might mean pushing back to the next release window to make sure this is manageable to produce a quality front-end to sit alongside the others. I wish to thank you those in the GCC developer community, who have inspired me and helped me navigate my journey to this point in time. - Thomas Schwinge - Mark Wielaard - Tom Tromey - Ian Lance Taylor - David Edelsohn - David Malcolm - Martin Jambor Thanks –Phil -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Invitation: GCC Rust community call @ Fri 1 Jul 2022 10am - 10:30am (BST) (gcc-rust@gcc.gnu.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20220701T09Z DTEND:20220701T093000Z DTSTAMP:20220627T151714Z ORGANIZER;CN=philip.her...@embecosm.com:mailto:philip.her...@embecosm.com UID:700eo29icvg5k3rpa1b4aki...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=gcc-rust@gcc.gnu.org;X-NUM-GUESTS=0:mailto:gcc-rust@gcc.gnu.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=philip.her...@embecosm.com;X-NUM-GUESTS=0:mailto:philip.herron@embecosm .com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=arthur.co...@embecosm.com;X-NUM-GUESTS=0:mailto:arthur.cohen@embeco sm.com X-MICROSOFT-CDO-OWNERAPPTID:621976092 CREATED:20220627T151712Z DESCRIPTION:Hi everyone\,Its th at time again for our monthly community call (on-time :-)).< span> \; - Date and Time 1st July 2022 at: \; \;Fri\, Jul 1 2022\, 0900 UTC&nb sp\; - Agenda: \;https://hackmd.io/L26Zcfs nT8q5YcadDSu1FQ">https://hackmd.io/L26ZcfsnT8q5YcadDSu1FQ&n bsp\;please feel free to add agenda items you wish to see discussed. \; - Jitsi: \;https://me et.jit.si/gccrs-community-callHope to see you there. Thanks --Philhttps://meet.jit.si/gccrs-community-call"; id="ow 740" __is_owner="true">\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit this section of th e description.\n\nView your event at https://calendar.google.com/calendar/e vent?action=VIEW&eid=NzAwZW8yOWljdmc1azNycGExYjRha2kxMGkgZ2NjLXJ1c3RAZ2NjLm dudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20wNzFhZDkxYTJmMWI2N2Y3M GY3ZTU5YTE4N2JmYjU0ZWZiOWIxMzQy&ctz=Europe%2FLondon&hl=en_GB&es=1.\n-::~:~: :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~ :~::- LAST-MODIFIED:20220627T151713Z LOCATION:https://meet.jit.si/gccrs-community-call SEQUENCE:0 STATUS:CONFIRMED SUMMARY:GCC Rust community call TRANSP:OPAQUE END:VEVENT END:VCALENDAR invite.ics Description: application/ics -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Invitation: GCC Rust hang out @ Weekly from 7pm to 7:30pm on Wednesday (BST) (gcc-rust@gcc.gnu.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+ TZOFFSETTO:+0100 TZNAME:BST DTSTART:19700329T01 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+ TZNAME:GMT DTSTART:19701025T02 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=Europe/London:20220629T19 DTEND;TZID=Europe/London:20220629T193000 RRULE:FREQ=WEEKLY;BYDAY=WE DTSTAMP:20220627T153913Z ORGANIZER;CN=philip.her...@embecosm.com:mailto:philip.her...@embecosm.com UID:4tl63v6qndrq0l26aisn0b4...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=philip.her...@embecosm.com;X-NUM-GUESTS=0:mailto:philip.herron@embecosm .com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=gcc-rust@gcc.gnu.org;X-NUM-GUESTS=0:mailto:gcc-rust@gcc.gnu.org X-MICROSOFT-CDO-OWNERAPPTID:218830682 CREATED:20220627T153912Z DESCRIPTION:Hi everyone\n\nThis is a regular call for anyone to drop in and talk about gccrs\, it should suit some people better with this time.\n\nWe will reuse our jitsi link: https://meet.jit.si/gccrs-community-call\n \n \ nThanks\n\n--Phil\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: ~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit this section of the descript ion.\n\nView your event at https://calendar.google.com/calendar/event?actio n=VIEW&eid=NHRsNjN2NnFuZHJxMGwyNmFpc24wYjRnNWogZ2NjLXJ1c3RAZ2NjLmdudS5vcmc& tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb21jZTllZWZiMzFkOWE1YmFkNDdlYzQ1ZGN iZWRjMzY0NWI2ZTZmZWUw&ctz=Europe%2FLondon&hl=en_GB&es=1.\n-::~:~::~:~:~:~:~ :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::- LAST-MODIFIED:20220627T153912Z LOCATION:https://meet.jit.si/gccrs-community-call SEQUENCE:0 STATUS:CONFIRMED SUMMARY:GCC Rust hang out TRANSP:OPAQUE END:VEVENT END:VCALENDAR invite.ics Description: application/ics -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Cancelled event with note: GCC Rust hang out @ Wed 6 Jul 2022 7pm - 7:30pm (BST) (gcc-rust@gcc.gnu.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:CANCEL BEGIN:VTIMEZONE TZID:Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+ TZOFFSETTO:+0100 TZNAME:BST DTSTART:19700329T01 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+ TZNAME:GMT DTSTART:19701025T02 RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=Europe/London:20220706T19 DTEND;TZID=Europe/London:20220706T193000 DTSTAMP:20220627T154013Z ORGANIZER;CN=philip.her...@embecosm.com:mailto:philip.her...@embecosm.com UID:4tl63v6qndrq0l26aisn0b4...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=philip .her...@embecosm.com;X-NUM-GUESTS=0:mailto:philip.her...@embecosm.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=gc c-r...@gcc.gnu.org;X-NUM-GUESTS=0:mailto:gcc-rust@gcc.gnu.org RECURRENCE-ID;TZID=Europe/London:20220706T19 CREATED:20220627T153912Z DESCRIPTION:Hi everyone\n\nThis is a regular call for anyone to drop in and talk about gccrs\, it should suit some people better with this time.\n\nWe will reuse our jitsi link: https://meet.jit.si/gccrs-community-call\n \n \ nThanks\n\n--Phil LAST-MODIFIED:20220627T154011Z LOCATION:https://meet.jit.si/gccrs-community-call SEQUENCE:1 STATUS:CANCELLED SUMMARY:GCC Rust hang out TRANSP:OPAQUE END:VEVENT END:VCALENDAR invite.ics Description: application/ics -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
