384 karma · joined March 23, 2025
Definitely a good clarification though yeah, important
Nitpick, but they absolutely can be split into several instructions, and this is the most common way it’s implemented on RISClike processors, and also single instructions aren’t necessarily atomic.
The actual guarantee is that the entire operation (load, store, RMW, whatever) occurs in one “go” and no other thread can perform an operation on that variable during this atomic operation (it can’t write into the low byte of your variable as you read it).
It’s probably best euphemismed by imagining that every atomic operation is just the normal operation wrapped in a mutex, but implemented in a much more efficient manner. Of course, with large enough types, Atomic variables may well be implemented via a mutex
* for add is 0.20 (ie 5 per cycle)
* for adc is 0.50 (ie 2 per cycle)
so it does seem correct.
This seems to be a consequence of `add` being available on ports 0, 1, 5, 6, & B, whereas `adc` is only available on ports 0 & 6
So yes as an individual instruction it’s no worse, but even non-dependent instructions will be worse for OoO execution (which is more realistic than viewing it as a single instruction)
While I get your point, it’s critical to recognise that betting 90% on a six being rolled doesn’t make you correct when a six is rolled. You can believe polymarket was truly mispriced even with this outcome
That being said, once it’s failed detonation (and you’ve cut off any possible signals to the detonator), wouldn’t you roughly expect it to be as dangerous as transporting one?
They mention the large chunk of ̶h̶i̶g̶h̶ secondary* explosive in there, but the key attribute of ̶h̶i̶g̶h̶ secondary explosives - by definition - is how hard they are to actually trigger. So the only failure mode is “somehow the detonator itself has entered a state that did not detonate with the initial signal, but will eventually detonate after >1hr”, which you’d _hope_(!) it was wired to prevent.
Again, I’d shit myself immediately in this scenario. Just interesting from an engineering perspective
*see comment below, `high` explosive does not mean "hard to detonate". Cursory searches for the [limited] information on the trigger-explosive used in nuclear weapons suggest they were mostly secondary explosives, and also will probably have put me on a new watchlist!
Which means you should (as a bayesian actor) update on it saying “I am X” as evidence it is X
This seems true but sort of vacuous. Obviously an arbitrary statement, much like that as a human, can only be determined "true"/"false" by rigorous first order logic.
But outside of binary T/F, wouldn't "grok says it is Claude 3.5 Sonnet yet other LLMs do not" make you update your chance that grok is actually just Claude 3.5 sonnet?
I wouldn't say I believe it with much conviction. But it seems irrational to not believe it _somewhat more_ after seeing this.
Describing LLMs as "next token predictors" is disingenuous and wrong
But right above this you made a statement about how they work. You can’t claim we know how they work to support your opinion, and then claim we don’t to break down the opposite opinion
If you’re doing it wrong to a meaningful extent you won’t be able to get insurance or it will be very expensive
More generally I think “if something is bad, we should not be able to insure it because then we incentivise it” is not right
What do you mean by this? I don’t think the understanding of LLMs is sufficient to make this claim