face6b61d5
This is an experimental proof of concept demo:
make -j8 o//examples/i386.i386.com
o//examples/i386.i386.com --32
echo $? # <-- prints main32's argc parameter
Please note there's no libc support at the moment. This change is just
for fun and shouldn't be interpreted as intent to support. Having this
project on the whole support i386 would be tough because the calling
conventions are so different. There really isn't much in the way of low
hanging fruit opportunities to do something like NOP out REX prefixes
and call it a day. It'd likely need disjoint builds or possibly better
yet really cleverly crafted code generation in //third_party/chibicc!
Another challenge is is that Linux changed its SYSCALL ordinals when it
migrated from i386 to x86_64. Linux used to use the same magic numbers
as everyone else for functions like exit/write/read/etc. BSDs on the
other hand didn't pointlessly renumber things. So we'd need to find a
way to define the ordinals in libc/sysv/syscalls.sh twice for Linux. The
same goes for other ISAs too. Especially MIPS. For the Linux Kernel
alone, syscall magic numbers and data structure layouts are totally
different, and that's likely the case for other ISAs on other operating
systems too. Probably because ISA code historically got contributed to
open source by the companies that made the chips. Ulrich Drepper wrote
an amusing essay on the subject some years back.
|
||
|---|---|---|
| .. | ||
| alg | ||
| bits | ||
| calls | ||
| crt | ||
| crypto | ||
| dns | ||
| elf | ||
| fmt | ||
| integral | ||
| intrin | ||
| isystem | ||
| linux | ||
| log | ||
| mem | ||
| nexgen32e | ||
| nt | ||
| ohmyplus | ||
| rand | ||
| runtime | ||
| sock | ||
| stdio | ||
| str | ||
| stubs | ||
| sysv | ||
| testlib | ||
| time | ||
| tinymath | ||
| unicode | ||
| x | ||
| zipos | ||
| assert.h | ||
| complex.h | ||
| dce.h | ||
| disclaimer.inc | ||
| errno.h | ||
| inttypes.h | ||
| libc.mk | ||
| limits.h | ||
| literal.h | ||
| mach.h | ||
| macho.internal.h | ||
| macros-cpp.internal.inc | ||
| macros.h | ||
| macros.internal.inc | ||
| math.h | ||
| notice.inc | ||
| notice.internal.h | ||
| paths.h | ||
| README.md | ||
| zip.h | ||
SYNOPSIS
Cosmopolitan Standard Library.
OVERVIEW
This directory defines static archives defining functions, like printf(), mmap(), win32, etc. Please note that the Cosmopolitan build configuration doesn't link any C/C++ library dependencies by default, so you still have the flexibility to choose the one provided by your system. If you'd prefer Cosmopolitan, just add $(LIBC) and $(CRT) to your linker arguments.
Your library is compromised of many bite-sized static archives. We use the checkdeps tool to guarantee that the contents of the archives are organized in a logical way that's easy to use with or without our makefile infrastructure, since there's no cyclic dependencies.
The Cosmopolitan Library exports only the most stable canonical system calls for all supported operating systems, regardless of which platform is used for compilation. We polyfill many of the APIs, e.g. read(), write() so they work consistently everywhere while other apis, e.g. CreateWindowEx(), might only work on one platform, in which case they become no-op functions on others.
Cosmopolitan polyfill wrappers will usually use the dollar sign naming convention, so they may be bypassed when necessary. This same convention is used when multiple implementations of string library and other performance-critical function are provided to allow Cosmopolitan to go fast on both old and newer computers.
We take an approach to configuration that relies heavily on the compiler's dead code elimination pass (libc/dce.h). Most of the code is written so that, for example, folks not wanting support for OpenBSD can flip a bit in SUPPORT_VECTOR and that code will be omitted from the build. The same is true for builds that are tuned using -march=native which effectively asks the library to not include runtime support hooks for x86 processors older than what you use.
Please note that, unlike Cygwin or MinGW, Cosmopolitan does not achieve broad support by bolting on a POSIX emulation layer. We do nothing more than (in most cases) stateless API translations that get you 90% of the way there in a fast lightweight manner. We therefore can't address some of the subtle differences, such as the nuances of absolute paths on Windows. Our approach could be compared to something more along the lines of, "the Russians just used a pencil to write in space", versus spending millions researching a pen like NASA.