/top/
/new/
/best/
/ask/
/show/
/job/
^
slacker news
login
about
←back to thread
Compiling C to Safe Rust, Formalized
(arxiv.org)
277 points
love2read
| 2 comments |
20 Dec 24 23:30 UTC
|
HN request time: 0.483s
|
source
Show context
jtrueb
◴[
21 Dec 24 01:14 UTC
]
No.
42476729
[source]
▶
>>42476192 (OP)
#
Interesting how higher optimization levels didn’t really help speed up rust in the O level comparison
replies(1):
>>42476747
#
1.
vlovich123
◴[
21 Dec 24 01:19 UTC
]
No.
42476747
[source]
▶
>>42476729
#
As they say it’s likely that the code they’re outputting is pessimizing rustc’s ability. Namely it sounds like they’re inlining code as part of the conversion
replies(1):
>>42476893
#
ID:
GO
2.
jtrueb
◴[
21 Dec 24 01:54 UTC
]
No.
42476893
[source]
▶
>>42476747 (TP)
#
Yes, I’m just saying how it kicks in basically immediately (O1).
↑