Hacker Newsnew | past | comments | ask | show | jobs | submit | washbear's commentslogin

This is not the reason. We created this branch in July 2025 (GCC 12.5 was released on 11 July, 2025) and spent a year stabilizing it. A new system compiler is considered far too much of a risky, incompatible change to backport. Especially since lots of C code no longer compiles with GCC 14+ without significant changes.

Each time we upgrade the system compiler, it requires extensive work to keep all of our supported architectures in working order, and adjust our code for compatibility.


Why would the C code no longer compile if it conforms to the spec?


"The spec" is loose in places and is full of undefined behavior which can change from compiler to compiler. Very low level code tends to hit these types of issues much more than application code would. But these types of issues are even common in large userspace codebases.


To me, undefined behavior is by default not conformant, so that wouldn't count for the purposes of my question.


There is more than one C specification, and with each new release of GCC several things that used to emit warnings are newly treated as errors.


but if the correct standard is specified as an option, shouldn't that prevent conformant applications from failing to compile in newer versions?


Sure, that's one approach. Testing those changes takes time when you're working on a whole operating system and a ports tree. More time than cutting a new gcc release, as it turns out.


> shouldn't that prevent

it should. It doesn't.


You sort of answered your own question.

Another reason is compiling with -Werror and hitting new warnings.

Also, the version of the spec changes with almost every major release.


Because, for some reason, someone at gcc decided that some warnings shall be treated as errors. Good luck finding out which those are and which flags you need as a countermeasure. Of course it has documentation. Of course it is useless.


This is partly the reason, the other reason is that we created this branch in July 2025 (GCC 12.5 was released on 11 July, 2025) and spent a year stabilizing it. A new system compiler is considered far too much of a risky, incompatible change to backport. Especially since lots of C code no longer compiles with GCC 14+ without significant changes.


People get "POSIX compliance" confused with "Unix certification". The first is an API you implement, the second is a rubber stamp.

All active Unix-like operating systems aim to implement the new interfaces as they're defined.


If that's your first target for removal, I'd wager a large amount of money that you're [unfamiliar](https://man.netbsd.org/compat_freebsd.8) with the NetBSD code base.


I only really have experience talking directly to the kernel abis, i.e. the stuff in netbsd/sys/kern/syscalls.master. I'm using sem_open / sem_wait / etc. as my futex replacement. What abi should I be using? https://github.com/jart/cosmopolitan/blob/master/third_party...


This is part of the contract all new committers are required to sign. Becoming a NetBSD committer requires membership of the NetBSD Foundation and there's an understanding that trust is expected.


The article is wrong, it has branding disabled (so it identifies as Nightly), but it's stable Firefox. And the linked article indicates that one compositor can be used.


Yes, X11 works. Feature chart here: https://wiki.netbsd.org/ports/evbarm/apple/


Not true; we have podman


The author of the post probably accidentally hit the Compose key before comma by mistake. Compose comma comma produces that character.

https://en.wikipedia.org/wiki/Compose_key

A very NetBSD mistake.


It's "big in Japan". Used on many ISP routers there, for example Internet Initiative Japan's "SEIL" family, as well as most workstations in a few Japanese universities.

pkgsrc enjoys mild popularity in the scientific computing community, a lot of NetBSD use is probably in education - Cambridge University uses it for their thin clients too.


Thanks!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: