pizlonator

6 ms·

61.
by pizlonator 3mo ago
I use AI all the time But I don't want the AI to summarize my email for me. I don't want the AI to summarize my calendar for me. I don't want the AI to summarize my Zoom call for me. Thanks
62.
by pizlonator 3mo ago
> Maybe for the multi modal? Yeah
63.
by pizlonator 3mo ago
I read a decent chunk of the rewrite. It’s inaccurate to call it a rewrite. It’s more a transliteration - it matches the original Zig almost exactly but the syntax is different. And yeah, unsafe blocks anywhere that rust would have complain
64.
by pizlonator 3mo ago
Yeah But the point is that at any moment, there is friction in switching
65.
by pizlonator 3mo ago
That makes sense, but I really do have to emphasize just how gloriously stable my old PC router setup was. It was the most incredibly hassle free router I've ever had. Hopefully, the OpenWrt One is like that. But if not, I'm going
66.
by pizlonator 3mo ago
What a coincidence to see this on the front page! I just received my OpenWrt One because I’m tired of dealing with the questionable quality of most routers. And I don’t feel like resurrecting my old PC that I used as a router for a while. I
67.
by pizlonator 3mo ago
How much water AI data centers use feels like the least interesting reason to dislike them. If I wanted to dislike them for environmental reasons, then I’d focus entirely on the energy consumption and CO2 emission from the generators direct
68.
by pizlonator 4mo ago
I meant descendant. Fixed.
69.
by pizlonator 4mo ago
You don’t have to be in the same function as the setkom; you just have to be in a frame that’s deeper in the stack, or the same frame The point about memory safety is really this: if I allowed you to longjmp but did not guard it adequately
70.
by pizlonator 4mo ago
Gotcha, that’s a good list. It’s true that Fil-C doesn’t try to protect you from those bugs. I just don’t think of those as the worst things that can happen when you misuse these APIs.
71.
by pizlonator 4mo ago
I’ve used the copy-stack trick before! It’s really great! You can work around the pointer relocation issue by always coping the stack back onto the main stack. So you’re always running on the same range of stack in memory and saved stacks a
72.
by pizlonator 4mo ago
> In comparison, ucontext is very heavy It's heavy because it switches the signal masks. Indeed, Fil-C's ucontext logic does this today, because I'm relying on glibc, and that's what glibc does. But it would be straig
73.
by pizlonator 4mo ago
What misuse are you imagining that isn’t a memory safety problem? You might find that Fil-C prevents those too. It’s pretty strict. You can only use longjmp to pop stack like an exception would
74.
by pizlonator 4mo ago
Claude only ever wrote some tests I have used Kimi K2.6-code and GLM 5.2, but only for things that are easy to verify. I did not use any LLMs for the longjmp/ucontext work.
75.
by pizlonator 4mo ago
These functions can easily be misused to corrupt memory, so they very much have something to do with safety. Fil-C goes to great lengths to prevent your use of those functions leading to memory corruption or any violation of the capability
76.
Memory Safe Context Switches(fil-c.org)
4 points by pizlonator 4mo ago|0 comments
77.
by pizlonator 4mo ago
Right That’s still in the OpenAI charter fwiw
78.
by pizlonator 4mo ago
It is super unfair It creates a two tier system - those who have access and those who do not. Worse, it’s some corpo making the decision
79.
by pizlonator 4mo ago
Correct.
80.
by pizlonator 4mo ago
Yeah Also, like, this is the initial implementation so I kept it consistent with the rest of the error checking If someone wants a compile time diagnostic they can submit a patch
81.
by pizlonator 4mo ago
> You have to understand that Fil-C primarily exists as a marketing stunt. What a bitter way to analyze a technology. > under some circumstances Fil-C considers it legal to read a value from a totally different, possibly-inaccessible
82.
by pizlonator 4mo ago
Ooh - I thought you meant adding boosts use of assembly to the list of inline asm use cases I get you now
83.
by pizlonator 4mo ago
It’s not inline assembly It’s module assembly They’re different
84.
by pizlonator 4mo ago
I was able to build it and a lot of it seemed to work There was some debugging thing where it embeds debug info using module level assembly that you have to disable.
85.
by pizlonator 4mo ago
It’s surprisingly hard to define „erroneously”, but that’s not far off from what I did Example of a bug found most recently was that sahf was allowed without a cc constraint. Anyway, if you find bugs, file them. Would be fun to see if there
86.
by pizlonator 4mo ago
Zero, since I made those programs work back when all inline asm was an error. So currently most of those still have the hacks to go down the no-inlineasm path when building with Fil-C For the few where I reinstated the inline assembly, ther
87.
by pizlonator 4mo ago
Your godbolt code used atomic_thread_fence The quote uses atomic_signal_fence. If you find a way to bypass my checks, file a bug. I tried very hard to break it. My agent loops tried even harder
88.
by pizlonator 4mo ago
> compliant at scale The jokes write themselves.
89.
by pizlonator 4mo ago
Lots of tests
90.
by pizlonator 4mo ago
Structs aren’t necessary for my proposal to work well

More ›