June 9, 2025 at 12:32 PM, "Philip Herron" mailto:herron.phi...@googlemail.com?to=%22Philip%20Herron%22%20%3Cherron.philip%40googlemail.com%3E
> wrote:
>
> Sounds good. Marc (dkm) is going to do a big push later tonight so
> this will help handle that.
>
Yes...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120018
--- Comment #3 from Marc Poulhiès ---
Ok, thanks Andrew, we'll take care of fixing this.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333
Marc Poulhiès changed:
What|Removed |Added
See Also||https://github.com/Rust-GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333
--- Comment #3 from Marc Poulhiès ---
Correct. Not sure about having a .cargo at toplevel currently, so I'll simply
--offline for bck, and we'll be able to revisit.
https://github.com/Rust-GCC/gccrs/pull/3505
--
You are receiving this mail bec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629
--- Comment #7 from Marc Poulhiès ---
There's no language spec yet, it's WIP:
https://github.com/rust-lang/rust/issues/113527
Currently, the reference is rustc and the goal is to match its current
behavior.
I think the frontend is not listed b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111
Marc Poulhiès changed:
What|Removed |Added
See Also||https://github.com/Rust-GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
Marc Poulhiès changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
--- Comment #3 from Marc Poulhiès ---
I can yes, but wasn't really sure and didn't want to interfere with Arthur
ongoing work at updating the gcc's master branch with all the pending changes
from github.
Should I submit the patch for formal app
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111
--- Comment #3 from Marc Poulhiès ---
Thanks Jonathan for the suggestion.
The lexer code still need some refactor because the Source type (2nd template
argument to buffered_queue) is expected to have a next() method and is used
with both a Inpu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111
--- Comment #1 from Marc Poulhiès ---
Hello David,
Looking at the errors, most of them are trivial to fix.
1-6: missing 'override'.
9: not present in most recent dev branch on github, can be ignored as it will
disappear when we update the gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
Marc Poulhiès changed:
What|Removed |Added
See Also||https://github.com/Rust-GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
Marc Poulhiès changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |dkm at gcc dot gnu.org
May 10, 2022 1:38 PM, "Mark Wielaard" wrote:
> On Tue, 2022-05-10 at 11:00 +, builder--- via Gcc-rust wrote:
>
>> A new failure has been detected on builder gccrust-debian-i386 while
>> building gccrust.
>>
>> Full details are available at:
>> https://builder.sourceware.org/buildbot/#builde
> Worker for this Build: debian-ppc64
Hi Mark,
Looks like the ppc64 is requesting a bigger disk :)
fatal: sha1 file
'/var/lib/buildbot/workers/wildebeest/gccrust-debian-ppc64/gccrs/.git/index.lock'
write error. Out of diskspace
Cheers,
Marc
--
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
http
Hey!
Looks like tests are not OK, at least in the github action. Can't test but
maybe you can confirm this issue ?
# of unexpected failures14
Marc
August 15, 2021 9:55 PM, "Mark Wielaard" wrote:
> Handle BOOL and FLOAT in ConstFoldExpr::visit (HIR::LiteralExpr) to
> make it possible
15 matches
Mail list logo
