[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Verifying Toolchain Semantics
From: |
Mark H Weaver |
Subject: |
Re: Verifying Toolchain Semantics |
Date: |
Fri, 03 Oct 2014 13:13:09 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (gnu/linux) |
Taylan Ulrich Bayirli/Kammer <address@hidden> writes:
> In your PDF analogy, the solution is to write a spurious
> amount of PDF implementations. Or for C, to implement a spurious amount
> of C compilers. That is impractical because C is complex. What might
> be practical might be to write one new C compiler (guaranteed clean,
> since it's new), and verify GCC with that[*]. What's more useful in the
> long term is to define a much simpler language, and base our everything
> on that instead of on C.
Okay, so why does he insist on using PDF to distribute an essay that is
just plain text anyway? He should practice what he preaches.
Mark
- Verifying Toolchain Semantics, Ian Grant, 2014/10/02
- Re: Verifying Toolchain Semantics, Mark H Weaver, 2014/10/03
- Re: Verifying Toolchain Semantics, Nala Ginrut, 2014/10/03
- Re: Verifying Toolchain Semantics, Ian Grant, 2014/10/04
- Re: Verifying Toolchain Semantics, Nala Ginrut, 2014/10/05
- Re: Verifying Toolchain Semantics, Ian Grant, 2014/10/05
- Re: Verifying Toolchain Semantics, Nala Ginrut, 2014/10/05
- Re: Verifying Toolchain Semantics, Ian Grant, 2014/10/05
- Re: Verifying Toolchain Semantics, Nala Ginrut, 2014/10/06
- Re: Verifying Toolchain Semantics, Mike Gerwitz, 2014/10/05
- Re: Verifying Toolchain Semantics, Ian Grant, 2014/10/05