Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Privilege Levels Below User
Date: Sun, 9 Jun 2024 22:48:28 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <v45bfr$3rcpa$9@dont-email.me>
References: <jai66jd4ih4ejmek0abnl4gvg5td4obsqg@4ax.com>
	<2ad84effd7f284445e0d8b90e0170f09@www.novabbs.org>
	<4fhb6jdpr1tlonfum9cccq9j1h2vrlo60j@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 10 Jun 2024 00:48:28 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="1186807d38ad523ecdef8690d71c9c11";
	logging-data="4043562"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19/OCWa4I4O78L2z+O0Jjx0"
User-Agent: Pan/0.158 (Avdiivka; )
Cancel-Lock: sha1:BEDQ2/TYD1kfU34FK2mGANpXv7o=
Bytes: 1614

On Sun, 09 Jun 2024 09:14:11 -0600, John Savard wrote:

> A C compiler doesn't save data in memory that can then be executed. It
> writes to a file.

That’s an implementation issue. Back in the day, there were such things as 
“load-and-go” compilers. E.g. the Waterloo Fortran that I used in some 
undergraduate courses. I’m sure people would have done ones for C.

These days, there are things called “JIT” (“just-in-time”) compilers.

And just as a further nitpick (if the above weren’t enough), what happens 
if the “file” your C compiler is writing to is in a RAM disk?