Re: [Toybox] __attribute__((__noreturn__)) vs _Noreturn

2022-05-10 Thread enh via Toybox
oh, and if you want to see the miscompile "in action", here's a godbolt link showing that [[noreturn]] and _Noreturn work in their respective languages, but __attribute__((__noreturn__)) is broken in C (but not C++!): https://godbolt.org/z/T6nMoa75G On Tue, May 10, 2022 at 3:08 PM enh wrote: > >

Re: [Toybox] __attribute__((__noreturn__)) vs _Noreturn

2022-05-10 Thread enh via Toybox
attached two separate patches; one to move, the other to take advantage of the move. given that `_Noreturn` is required to be at the start, i kind of wish they'd made it imply `void`; `noreturn void` seems a bit redundant! On Tue, May 10, 2022 at 11:00 AM enh wrote: > > On Tue, May 10, 2022 at

Re: [Toybox] __attribute__((__noreturn__)) vs _Noreturn

2022-05-10 Thread enh via Toybox
On Tue, May 10, 2022 at 10:44 AM Rob Landley wrote: > > On 5/9/22 18:54, enh via Toybox wrote: > > i think this question already came up recently, but mainly as a joke > > before ... "how do you feel about C11?" > > It's comfortably past the 7 year support horizon. I haven't got anything >

Re: [Toybox] __attribute__((__noreturn__)) vs _Noreturn

2022-05-10 Thread Rob Landley
On 5/9/22 18:54, enh via Toybox wrote: > i think this question already came up recently, but mainly as a joke > before ... "how do you feel about C11?" It's comfortably past the 7 year support horizon. I haven't got anything against C11, I just haven't needed anything from it yet? Actually, I

Re: [Toybox] Android .config pondering.

2022-05-10 Thread enh via Toybox
On Tue, May 10, 2022 at 7:45 AM Rob Landley wrote: > > On 5/9/22 19:37, enh wrote: > > On Sat, May 7, 2022 at 4:38 AM Rob Landley wrote: > >> > iirc the reason they differ is that macos_defconfig is "everything > >> > that passes the tests on a mac [the last time enh ran all the tests on > >> >

Re: [Toybox] Android .config pondering.

2022-05-10 Thread Rob Landley
On 5/9/22 19:37, enh wrote: > On Sat, May 7, 2022 at 4:38 AM Rob Landley wrote: >> > iirc the reason they differ is that macos_defconfig is "everything >> > that passes the tests on a mac [the last time enh ran all the tests on >> > a mac]" whereas the android mac config is basically "the