Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Thu, 12 Sep 2024 03:12:11 -0700
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <867cbhgozo.fsf@linuxsc.com>
References: <2024Aug30.161204@mips.complang.tuwien.ac.at> <86r09ulqyp.fsf@linuxsc.com> <2024Sep8.173639@mips.complang.tuwien.ac.at> <2024Sep10.101932@mips.complang.tuwien.ac.at> <2024Sep11.123824@mips.complang.tuwien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Thu, 12 Sep 2024 12:12:12 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="62297a80a79ef9d9a88587ce28522bc2";
logging-data="209847"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18+ytLDkjkrex4d1MbLukrmQvmQh9DTcug="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:lCfHmVmsxVBJXBxH/YJxgjb6I+E=
sha1:jJoUTxzcLS/Fm76Jps9puj/NWXo=
Bytes: 2047
BGB writes:
[...]
> Would be nice, say, if there were semi-standard compiler macros for
> various things:
> Endianess (macros exist, typically compiler specific);
> And, apparently GCC and Clang can't agree on which strategy to use.
> Whether or not the target/compiler allows misaligned memory access;
> If set, one may use misaligned access.
> Whether or not memory uses a single address space;
> If set, all pointer comparisons are allowed.
>
> [elaborations on the above]
I suppose it's natural for hardware-type folks to want features
like this to be part of standard C. In a sense what is being
asked is to make C a high-level assembly language. But that's
not what C is. Nor should it be.