[Bug rust/114629] rust-ast-resolve-expr contains bloated code for funny_error

2024-04-08 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629

Pierre-Emmanuel Patry  changed:

   What|Removed |Added

 CC||pierre-emmanuel.patry@embec
   ||osm.com

--- Comment #2 from Pierre-Emmanuel Patry  ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/116427] [15 regression] 32-bit crab1 fails to link on Solaris

2024-08-20 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116427

Pierre-Emmanuel Patry  changed:

   What|Removed |Added

 CC||pierre-emmanuel.patry@embec
   ||osm.com

--- Comment #1 from Pierre-Emmanuel Patry  ---
(In reply to Rainer Orth from comment #0)

> I wonder what the way forward is here: just wait for gccrs to be
> self-contained
> and cargo is no longer needed to bootstrap?

>From what I can see on the list of supported target
https://doc.rust-lang.org/nightly/rustc/platform-support.html, rustc
does not support solaris 32bits. We will have to wait for gccrs to be
self-contained.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)

2025-03-18 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353

--- Comment #3 from Pierre-Emmanuel Patry  ---
This version of polonius is built with a nightly feature but we backported it
to stable in another commit. As we didn't want to send too many patches at once
we split the upstream process in four batches. The commit fixing this should
land soon in upstream.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

2025-04-08 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #7 from Pierre-Emmanuel Patry  ---
89ca1e3cb697a87f02682a1fb1f62f02d0671c57 Should have fixed this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

2025-03-28 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #1 from Pierre-Emmanuel Patry  ---
There is something funny happening here because canonical_paths1.rs should not
pass, nr2 tests are a list of test with an additional flag. We're using it to
reduce the gap between both name resolution.

Does XPASSEs happen solely on Solaris or does it also happen on x86_64 ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

2025-03-28 Thread pierre-emmanuel.patry at embecosm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #5 from Pierre-Emmanuel Patry  ---
(In reply to Andrew Pinski from comment #4)
> I wonder if it is showing up due to running the testsuite with -jN

It is indeed showing up with -jN on my machine. Good call!

-- 
You are receiving this mail because:
You are on the CC list for the bug.