_g6sn

4 ms·

1.
by _g6sn 1y ago
(I'll address the parallel build part in addition to what has been said, but please respond to my email address/sourcehut mailing list for any further communication on these issues). I should have communicated this more clearly in
2.
by _g6sn 1y ago
Thank you. On that subdomain, nothing was generated -- I just sat down and typed it in the editor for no particular reason. Should have validated it, at least Edit: The external source archive page was. Although, with a very simple bash scr
3.
by _g6sn 1y ago
Yes, indeed, libc behavior (at minimum) is defined by the standard itself, and the compiler has to ensure that the library is functional. I have explicitly acknowledged it in my comment above ("this is my problem as a compiler develope
4.
by _g6sn 1y ago
I am going to hijack this comment for a little rant about libc and independent compilers. Existing libc implementations have varying levels of hostility towards non-gcc/clang compilers. Glibc is probably the worst offender here, musl i
5.
by _g6sn 1y ago
I have addressed compiler inefficiency in the sibling comment. This is indeed a problem. Empty arrays of such size should be compile-able (there is sparse representation for arrays). However, I would say that this use case is not particular
6.
by _g6sn 1y ago
(I thought that the announcement has completely faded, so haven't even checked the replies). I'll immediately reveal some issues with the project. On the compilation speed, it is unfortunately atrocious. There are multiple reasons
7.
Kefir: Solo-developed full C17/C23 compiler with extensive validation(kefir.protopopov.lv)
64 points by _g6sn 1y ago|21 comments
8.
by _g6sn 4y ago
Kefir author here. Quite surprised to see it on HN. A few notes in response to Brian's post and comments: - Kefir name is simply a reference to milk drink, no other connotation is intended. Updated project README with this information.