How big is the stack? Too often large data will blow the top and destroy adjacent stacks in multi-thread environments. Are memory barrier fences used to check against overflow?
I think it is supposed to be stacks in the general sense of the data structure, not the literal `sp` register. I imagine they could be arbitrarily sized up to physical limits if you do some mmap magic. I'm still a bit fuzzy about how you could make useful programs with that, but it seems interesting.
I’m not a fan of this kind of “fancy” optimization anyway.
It’s too fragile. I may make some innocuous change, now the compiler cannot recognize the pattern and performance falls off the cliff.
I’d rather have the reliabile performance than the absolute fastest possible result. Then if there’s an issue I can catch and fix it reliably with profiling, not deal with a heisenbug based on whether the compiler can match the pattern.
I don't know. AI are basically trained to tell you what you want to hear, including when they're disagreeing with you. If you come off of your conversation with AI with a stronger belief than when you went in, is that merited?
"AI Advice Suppresses People’s Willingness To Say “I Don’t Know”, Even When The Advice Is Wrong And Accuracy Is Incentivized" https://osf.io/preprints/psyarxiv/5y6m4_v1
Yeah you have to frame the prompt as if you've come across some potentially extremist view you want to know more about, and pretend you're an outsider needing advice. Then you bias it to favor what you really want to know.
reply