mirror of https://codeberg.org/ziglang/zig.git synced 2025-12-07 22:34:28 +00:00

History

Alex Rønne Petersen c8ca05e93a std.Target: Remove `sparcel` architecture tag. What is `sparcel`, you might ask? Good question! If you take a peek in the SPARC v8 manual, §2.2, it is quite explicit that SPARC v8 is a big-endian architecture. No little-endian or mixed-endian support to be found here. On the other hand, the SPARC v9 manual, in §3.2.1.2, states that it has support for mixed-endian operation, with big-endian mode being the default. Ok, so `sparcel` must just be referring to SPARC v9 running in little-endian mode, surely? Nope: * `40b4fd7a3e/llvm/lib/Target/Sparc/SparcTargetMachine.cpp (L226)` * `40b4fd7a3e/llvm/lib/Target/Sparc/SparcTargetMachine.cpp (L104)` So, `sparcel` in LLVM is referring to some sort of fantastical little-endian SPARC v8 architecture. I've scoured the internet and I can find absolutely no evidence that such a thing exists or has ever existed. In fact, I can find no evidence that a little-endian implementation of SPARC v9 ever existed, either. Or any SPARC version, actually! The support was added here: https://reviews.llvm.org/D8741 Notably, there is no mention whatsoever of what CPU this might be referring to, and no justification given for the "but some are little" comment added in the patch. My best guess is that this might have been some private exercise in creating a little-endian version of SPARC that never saw the light of day. Given that SPARC v8 explicitly doesn't support little-endian operation (let alone little-endian instruction encoding!), and no CPU is known to be implemented as such, I think it's very reasonable for us to just remove this support.		2024-07-30 06:30:25 +02:00
..
aro	std.Target: Remove `sparcel` architecture tag.	2024-07-30 06:30:25 +02:00
backend	Update uses of `@fieldParentPtr` to use RLS	2024-03-30 20:50:48 -04:00
aro.zig
backend.zig
README.md	Sync Aro sources (#19199 )	2024-03-06 14:17:41 -05:00

README.md

Aro

A C compiler with the goal of providing fast compilation and low memory usage with good diagnostics.

Aro is included as an alternative C frontend in the Zig compiler for translate-c and eventually compiling C files by translating them to Zig first. Aro is developed in https://github.com/Vexu/arocc and the Zig dependency is updated from there when needed.

Currently most of standard C is supported up to C23 and as are many of the common extensions from GNU, MSVC, and Clang

Basic code generation is supported for x86-64 linux and can produce a valid hello world:

$ cat hello.c
extern int printf(const char *restrict fmt, ...);
int main(void) {
    printf("Hello, world!\n");
    return 0;
}
$ zig build && ./zig-out/bin/arocc hello.c -o hello
$ ./hello
Hello, world!