> That doesn't sound like it lets me increment any stack address I want and store into the resulting pointer.
Why not?
> And are return values still on the same stack?
Other implementation-defined things might have addresses too, those things just aren't variables. I think you might be able to still allow inlining without UB if you make it implementation-defined per call-site what other things might get addresses.
Re:Modern C (2019)
by Dylan16807 on Friday June 02, 2023 @03:43PM
(#36169878)
> Why not?
At this point the conversation has completely converged so I'm only going to reply over here: https://news.ycombinator.com/item?id=36169808
That doesn't sound like it lets me increment any stack address I want and store into the resulting pointer.
And are return values still on the same stack? I probably should have said I meant the traditional kind of C stack.