In-Reply-To: <7A721AF1-9D9B-4F7A-9E67-F0E8FB989E7D@freebsd.org>
index | | previous in thread | raw e-mail
On Mon, Feb 09, 2026 at 08:22:58PM +0000, Jessica Clarke wrote: > > On 9 Feb 2026, at 19:07, Konstantin Belousov <kib@FreeBSD.org> wrote: > > > > The branch main has been updated by kib: > > > > URL: https://cgit.FreeBSD.org/src/commit/?id=31fab773613b21183fbd5a313fa8c69d37fcb196 > > > > commit 31fab773613b21183fbd5a313fa8c69d37fcb196 > > Author: Konstantin Belousov <kib@FreeBSD.org> > > AuthorDate: 2026-02-05 19:40:55 +0000 > > Commit: Konstantin Belousov <kib@FreeBSD.org> > > CommitDate: 2026-02-09 18:57:19 +0000 > > > > sys/compat/freebsd32: use freebsd32_uint64_t for struct kinfo_proc32 > > Can we please go with my __aligned(4) suggestion for > freebsd32_uint64_t? FU64_CP is getting all over the place now and has > no good reason to exist when we can readily use a GNU C feature we’re > already using in other ways. I strongly prefer to keep using std C instead of gnu extension when possible. In this case it is possible. FU64_CP() might be wrapped into CP() with some use of _Generic(). I might look at this later.home | help