#fix can't use gdb for debug #26
Open
This pull request is big! We’re only showing the most recent 250 commits.
Commits on Oct 15, 2020
-
-
-
-
-
-
_Bool isn't just a 1-bit integer because when you convert a value to bool, the result is 1 if the original value is non-zero. This is contrary to the other small integral types, e.g. char, as you can see below: char x = 256; // x is 0 _Bool y = 256; // y is 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Allow to omit array length if an initializer is given
So that you can write something like `int x[] = {1, 2, 3}` instead of `int x[3] = {1, 2, 3}`. -
-
-
-
-
-
-
-
-
-
-
-
Accept
voidas a parameter list`foo(void)` indicate that function foo does not take a parameter.
-
-
-
-
-
-
-
-
-
-
-
-
Handle a function returning bool, char or short
x86-64 psABI says that only the least significant 8 bits are significant if RAX has a return value of a function returning bool. Likewise, it looks like only the least significant 1 or 2 bytes are guaranteed to have a correct value for char and short return values, respectively.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Dereferencing a function shouldn't do anything
This is an oddity in the C spec, but you can apply the unary `*` operator to a function as many times as you want. `*x` and `x` means exactly the same, given that `x` is a function.
-
-
-
-
-
-
-
-
-
Write to an in-memory buffer before writing to an actual output file
We don't want to leave a partial assembly output if the compiler fails during compilation. Technically speaking, there's still a risk of leaving a partially- written output file if the compiler dies during file copy. To fix that, we have to write to a temporary file in the same filesystem as the final output file and rename the temporary file to atomically replace the output file. We don't do that in this patch for the sake of succinctness, though.
-
-
-
Make an array of at least 16 bytes long to have alignment of at least…
… 16 bytes Quote from AMD64 System V ABI: "An array uses the same alignment as its elements, except that a local or global array variable of length at least 16 bytes or a C99 variable-length array variable always has alignment of at least 16 bytes."
-
-
-
-
-
-
-
Accept multibyte character as wide character literal
On most Unix-like systems, wide character literal is 32-bit long and encodes a Unicode code point. On Windows, that is 16-bit long and encodes a UTF-16 code unit. Clearly, there's a portability issue here. Personally I've never used wide characters in my code as I didn't find it useful. Being said that, some header files contain wide character literal, so we need to support that so that chibicc can include such files. We assume that source files are always encoded in UTF-8.
-
-
-
-
-
-
-
-
-
Define __STDC_UTF_{16,32}__ macros
These predefined macros indicates that our u and U chars/strings are UTF-16 and UTF-32-encoded, respectively.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Commits on Oct 16, 2020
Commits on Nov 18, 2020
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.