Ah.. “success” means built without warnings and all tests pass. > On 5 Apr 2026, at 01:07, Benjamin Oldenburg <[email protected]> > wrote: > > Hi gr, > > alright. I will rewrite the history accordingly. > > The current state for https://github.com/bold84/tinycc/tree/win_arm64_clean : > > - arm64-win32 > - Clang: success > - MinGW GCC: not run > - MSVC cl: success > - x86_64-win32 > - Clang: not run > - MinGW GCC: success > - MSVC cl: success > Linux x86_64 > - GCC: success > - Clang: not installed > Linux aarch64 > - GCC: success > - Clang: not installed > macOS ARM64 (Darwin) > - Clang: success > > Any other targets that need to be green? > > Kind regards, > > Ben > > >> On 5 Apr 2026, at 00:52, grischka <[email protected]> wrote: >> >> On April 4, 2026 11:10:11 AM UTC, Benjamin Oldenburg >> <[email protected]> wrote: >>> I can complete the implementation in >>> https://github.com/bold84/tinycc/tree/win_arm64_clean if there’s a chance >>> it will actually be merged. >> >> Hi Ben, >> sure it will, great work. >> >> It would make sense though if we could somewhat compress the history to say >> less than 10 commits each addressing a theme such as for example generator, >> asm, runtime, symbolic replacement, etc. (while omitting unrelated >> whitespace changes and some stuff that we maybe dont really need also). Just >> a suggestion though ;) >> >> Some first approach of mine here: >> https://github.com/gr8001/tinycc/tree/arm64-win32 >> >> Greetings, >> -- gr >> >>> >>> Kind regards, >>> >>> Ben >>> >>> >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
