Date: Mon, 9 Feb 2026 20:22:58 +0000 From: Jessica Clarke <jrtc27@freebsd.org> To: Konstantin Belousov <kib@FreeBSD.org> Cc: "src-committers@freebsd.org" <src-committers@FreeBSD.org>, "dev-commits-src-all@freebsd.org" <dev-commits-src-all@FreeBSD.org>, "dev-commits-src-main@freebsd.org" <dev-commits-src-main@FreeBSD.org> Subject: Re: git: 31fab773613b - main - sys/compat/freebsd32: use freebsd32_uint64_t for struct kinfo_proc32 Message-ID: <7A721AF1-9D9B-4F7A-9E67-F0E8FB989E7D@freebsd.org> In-Reply-To: <698a3057.34751.45778dc0@gitrepo.freebsd.org>
index | next in thread | previous in thread | raw e-mail
> 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. Jessicahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7A721AF1-9D9B-4F7A-9E67-F0E8FB989E7D>