Re: [Tinycc-devel] bug in preprocessor

Fred van Kempen via Tinycc-devel [18/01/2024 21.35]: This: #include #include int main(int argc, char **argv) { #ifdef FOO     printf("Foo: %s\n", argv[0]); #endif  bar     return argc; } should not compile, for obvious reasons, but it does.. Using 0.28rc. It also compiles, with a

Re: [Tinycc-devel] Any plans to support utf8/utf16 string literals?

Am 15.01.24, 08:27 schrieb Brad Robinson via Tinycc-devel :> Just wondering if there are any plans to add support for utf8 (aka u8"string")> and utf16 (aka u"string") string literals in tcc?I also would like this c11 feature to be supportedand I have an old patch to detect thisbut it is not used

Re: [Tinycc-devel] bug in preprocessor

> To put some text after #endif on the same line, this used to be customary> in > K age, wasn't it?Yes, and that has evolved into using comment markers > there, likein #endif    /*foo*/ for example. > There are K sources still valuable today and it is really useful that > Tinycc is capable

Re: [Tinycc-devel] bug in preprocessor

> It also compiles, with a warning, both with GCC (13.2.0) and Clang > (15.0.7).It should generate a warning, yes. Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] SIMD intrinsics

Am 15.01.24, 08:57 schrieb Mathias Widman :> I am new to the list so forgive my lack of knowledge of previous questions.Welcome here, Mathias.> I wonder if there are any plans on incorporating/supporting SIMD intrinsics.Which target processor / which intrinsics?intrinsics