Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust

arnold@freefriends.org
Wed, 14 May 2025 08:21:51 +0000

          From comp.compilers
Related articles
Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust johnl@taugh.com (John R Levine) (2025-05-09)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust derek-nospam@shape-of-code.com (Derek) (2025-05-13)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust arnold@freefriends.org (2025-05-14)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust 643-408-1753@kylheku.com (Kaz Kylheku) (2025-05-14)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust anton@mips.complang.tuwien.ac.at (2025-05-15)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust gneuner2@comcast.net (George Neuner) (2025-05-15)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust christopher.f.clark@compiler-resources.com (Christopher F Clark) (2025-05-16)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust cross@spitfire.i.gajendra.net (2025-05-16)
Re: Paper: PR2: Peephole Raw Pointer Rewriting with LLMs for Translating C to Safer Rust 643-408-1753@kylheku.com (Kaz Kylheku) (2025-05-16)
| List of all articles for this month |
From: arnold@freefriends.org
Newsgroups: comp.compilers
Date: Wed, 14 May 2025 08:21:51 +0000
Organization: Compilers Central
References: 25-05-004 25-05-005
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="90205"; mail-complaints-to="abuse@iecc.com"
Keywords: Rust
Posted-Date: 14 May 2025 14:13:00 EDT

In article 25-05-005,
Derek <derek-nospam@shape-of-code.com> wrote:
>I suspect that the same is happening with Rust. If so, how does using
>Rust make the code safer than using C without any checking switched
>on?


Rust catches many problems at compile time. I am not at all a Rust
expert, or even a novice, but I don't think Rust does runtime
bounds checking, since it relies on compiler analysis instead.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.