diff options
| author | 2025-12-29 16:28:28 +0000 | |
|---|---|---|
| committer | 2026-02-16 19:11:24 +0000 | |
| commit | 2088b61f3d6053d3879dcfcbe91c00157d050e16 (patch) | |
| tree | 5633150ddabf0380577338bccab8b972f71f0013 /src/chunklets/README-x86 | |
| parent | 8d4b47298b6c9eeb9a3f79a5b80d894f80ed4a45 (diff) | |
| download | sst-2088b61f3d6053d3879dcfcbe91c00157d050e16.tar.gz sst-2088b61f3d6053d3879dcfcbe91c00157d050e16.zip | |
Make x86 library a little bit smaller again
Diffstat (limited to 'src/chunklets/README-x86')
| -rw-r--r-- | src/chunklets/README-x86 | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/src/chunklets/README-x86 b/src/chunklets/README-x86 index cbfcb5d..e280b51 100644 --- a/src/chunklets/README-x86 +++ b/src/chunklets/README-x86 @@ -30,13 +30,14 @@ Note that GCC and Clang will generally give the best-performing output. Once the .c file is built, the public header can be consumed by virtually any C or C++ compiler, as well as probably most half-decent FFIs. -Note that the .c source file is probably C++-compatible at the moment, but this -is not guaranteed, so it's best to compile it as a C source. The header will -work fine from either language. +Note that the .c source file is not C++-compatible, only the header is. The +source file relies on array designated initialisers, which are only standardised +in C. Some C++ compilers may still allow this with a warning, but the most +straightforward thing would be to compile the source using a C compiler. == API usage == -See documentation comments in x86.h for a basic idea. Some *pro tips*: +See documentation comments in x86.h for a basic idea. == OS compatibility == |
