Evan Haas

Single-narrow-char char literals should be sign extended on platforms where `char` is signed.

1

The following issues no errors on `x86_64-linux` but 2 errors for aro: ```c _Static_assert('\xFF' == -1, ""); #if '\xFF' != -1 #error comparison failed #endif ``` This only applies to...

### Zig Version 0.13.0-dev.4+c7ffdbcd4 ### Steps to Reproduce and Observed Behavior ```zig const std = @import("std"); test { var list = std.ArrayListAligned(u8, 4).init(std.testing.allocator); defer list.deinit(); try list.appendNTimes(1, 4); _ =...

Using the following test case in the test runner causes a memory leak ```c #define NO_ERROR_VALIDATION #define h(x) x(0) #define s() h(s) ``` ``` error(gpa): memory address 0x10c89f500 leaked: /Users/ehaas/local/zig-macos-x86_64-0.13.0-dev.44+9d64332a5/lib/std/array_list.zig:457:67:...

GCC and clang behave differently with regard to unsuffixed integer literals; see comment here https://github.com/ziglang/zig/issues/19701#issuecomment-2067190162 Note: MSVC follows the clang behavior of promoting to unsigned long long The current behavior...

This doesn't issue an error even though it should: ```c #if 1 < ABC 2 #endif ``` Identifiers, preprocessor numbers, and unary operators all seem to be incorrectly allowed currently....

```c int foo(void); int bar(void) { return ({foo;})(); } ``` This should parse without errors but we get: ``` test.c:3:20: error: expected ';', found '(' return ({foo;})(); ^ ```

std.math.big.int.Managed: panic during printing of large integers

1

### Zig Version 0.13.0-dev.44+9d64332a5 ### Steps to Reproduce and Observed Behavior ```zig const std = @import("std"); /// 2**2624 const large_number = "7992978086026108130997763255271161054080232827028600926878720894626652959801126270181797858326539991808408501955736107211154089990880864133038492082242191005916626161786978154573691945393533534978528355014105088982291537161053152762247775679110034623793214880221822114791083764160121545158487346802968250797762918640822953726116267698324397972187098127467165312071016262496415446666524545989368685880483796761627291294104820031154953033398353527633219044576542971747588932919682723327383286444096495073061099816572815545646462399372759381873394869194849561982777842027295205127497543421120520478507405494463168887803685629450345554505826605909746350048296170530667798848741774249115342399979893391684184998084322821589461452070845054017545885544579571298686351226398527864005606439403913216"; test { // BigInt docs state: // If...

```c unsigned char x = 1000; ``` We currently issue no warning; it should look something like: ``` test.c:1:19: warning: implicit conversion from 'int' to 'unsigned char' changes value from...

```c _BitInt(10) x = 1.2; ``` Currently our warning looks like this: ``` test.c:1:17: warning: implicit conversion from 'double' to '_BitInt' changes value from 1.2 to 1 [-Wfloat-conversion] _BitInt(10) x...