Re: ☠ Buildbot (Sourceware): gccrust - failed compile (failure) (master)
Hi,
please keep me in the loop for this one. I need cargo for the borrow checker as
well (the external Polonius engine).
Best
Jakub
On Thu, 29 Feb 2024, at 21:22, Mark Wielaard wrote:
> Hi,
>
> On Thu, Feb 29, 2024 at 09:00:13PM +0100, Thomas Schwinge wrote:
> > Three 'cargo' ('command not found') as well as
> > one 'rustc' ('error[E0658]: `let...else` statements are unstable')
> > errors:
>
> Yeah, I noticed those earlier, but oddly the tree became compilable
> again earlier today, then broke again?
>
> I think what needs to happen is have a config check for the minimum
> versions of cargo and rustc that are now needed for when configuring
> for --enable-languages=rust.
>
> Then we need to see for which builder arches/distros those versions of
> cargo and rustc are available and install them there (and disable the
> builders for which there is no good version available).
>
> Cheers,
>
> Mark
>
Re: [Bug rust/114629] rust-ast-resolve-expr contains bloated code for funny_error
There is no specification right now. Just reference implementation. The rustc team is working on it, but it will take a long time and it is not a priority. There is a language reference, but it is far from the completeness you would need from specification. BTW, I think it is funny. On Tue, 9 Apr 2024, at 02:11, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629 > > --- Comment #5 from Andrew Pinski --- > (In reply to Pierre-Emmanuel Patry from comment #2) > > I can see the problem with the message, but I don't think we can remove the > > behavior as we have to match rustc's behavior. The compiler has to ICE when > > meeting this identifier. I suggest changing the message to rustc's one "It > > looks like you're trying to break rust; would you like some ICE?" and > > removing the "gcc" identifier check. > > Really this sounds like a bad idea to copy 100% of what rustc does. Instead we > should follow the rust language specification (hopefully that actually > exists). > > While you are at it, it would be useful to add a link to the rust langauge > specification (like there is for almost all other languages [I see objective-C > is not listed]) to https://gcc.gnu.org/readings.html . > > -- > You are receiving this mail because: > You are on the CC list for the bug.
