News for hackers. Stuff that matters.

A comment on GCC Rust Approved by GCC Steering Committee. Parent comment

Re:GCC Rust Approved by GCC Steering Committee by zetaposter on Monday July 11, 2022 @01:43PM (#32059235)
1. GCC has more backends than LLVM. 2. Competition is good in general. 3. I expect this will trigger inconsistencies between GCC and rustc; because Rust doesn't really have a specification. Which will force both parties to discuss and solve them.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by tomjakubowski on Monday July 11, 2022 @02:58PM (#32060238)
Being on gcc, a long-lived platform, also helps ensure the survival of the language even if development of the current compiler (or LLVM) dies or withers.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by duckerude on Monday July 11, 2022 @03:19PM (#32060506)
Does it? GCC's Java frontend died and is no longer shipped, they need maintainers like any other compiler.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by genewitch on Monday July 11, 2022 @04:45PM (#32061577)
GCJ is no more? It was being used within recent memory for things, i thought.

I am out of the loop though, so if this is true, that's interesting and a bit weird.

[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by pjmlp on Monday July 11, 2022 @06:11PM (#32062693)
Since 2009 actually.

Most contributors eventually moved into OpenJDK after it became available.

GCC folks left it around for a couple of years, because GCJ unit tests exercised parts of the compiler no one else did.

Eventually they decided it wasn't worth that maintenance cost to keep it around only for that purpose.

[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by apple4ever on Monday July 11, 2022 @05:46PM (#32062372)
GCC support of Objective-C is very very poor.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by pjmlp on Monday July 11, 2022 @06:12PM (#32062705)
It is at the level NeXT was forced to contribute back to upstream.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by astrange on Monday July 11, 2022 @07:18PM (#32063432)
Reimplementing ObjC 2.0 would be very hard. You have to be precisely bug-compatible with Clang to implement ARC correctly.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by israrkhan on Monday July 11, 2022 @02:50PM (#32060128)
and to back up your point... There should be at least 2 implementations for anything to be a spec/standard.
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by faisal_ksa on Monday July 11, 2022 @01:47PM (#32059287)
Thank you so much. The specification point is very important
[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by netheril96 on Monday July 11, 2022 @09:26PM (#32064462)
> I expect this will trigger inconsistencies between GCC and rustc; because Rust doesn't really have a specification. Which will force both parties to discuss and solve them.

More likely that GCC has to follow all the bugs and quirks of rustc or no people will use GCC for Rust.

[ Parent | on HN ]
Re:GCC Rust Approved by GCC Steering Committee by nickitolas on Tuesday July 12, 2022 @09:57AM (#32070006)
> 1. GCC has more backends than LLVM

Did you mean target platforms? If so, how is this not already addressed by the rustc gcc (Via libgccjit) backend?

[ Parent | on HN ]