Currently, cuda to amdgpu. Product is at https://docs.scale-lang.com/stable/manual/how-to-install/, please email jon at spectralcompute.com if it misbehaves.
Libxml2 segv when the input is large and the transform complicated was something of a surprise to me. Parsing xml is easy enough but I think implementing xslt is going to be a nuisance.
Scale is a cuda implementation running on nvidia or amdgpu. Think nvcc semantics with template diagnostics by clang.
Nvidia including Spectral in their inception programs seems a big deal to me. It bodes well for the future of the cuda ecosystem.
If you'd like to run it, docs and download at https://scale-lang.com/. It's a clang fork with a bunch of libraries packaged. I'm on the dev team and always happy to hear from people.
Not imaginary. Eliding checks on nullptr and integer overflow were both implemented, shipped, miscompiled the linux kernel and grew flags to disable them. I expect there are more if one goes looking.
Well, you can't write malloc in conforming C, which hurts rather more than remembering to write bitcast as memcpy on char pointers.
Doesn't matter though because you aren't writing standards conforming C. You're writing whatever dialect your compilers support, and that's probably (module bugs) much better behaved than the spec suggests.
Or you're writing C++ and way more exposed to the adversarial-and-benevolent compiler experience.
The type aliasing rules are the only ones that routinely cause me much annoyance in C and there's always a workaround, whether if it's the launder intrinsic used to implement C++, the may_alias attribute or in extremis dropping into asm. So they're a nuisance not a blocker.
2. Persuading a mathematician to look closely at it
3. Announcing success if they conclude it is a proof
This is deeply disappointing relative to "chatgpt found a proof that isabelle verifies" or similar, especially the part where a mathematician spends (presumably hours) reading through the llm output.
Ymmv. I've got a mix of cheap premade patch cables and some I crimped from solid core, all cat5e, all holding 10gbe totally happily. I suspect that only works because they're a meter or two long but that reaches across the rack.
This was _really_ surprising to me. What's the point of marking individual stores if it affects everything, not just that address. But yeah, what I can find online agrees that C++ has done this. Thanks!
I've stopped reading anything on blogs on the basis that it's now probably llm spew and life is too short for the signal to noise ratio that implies.
With the exception of things that places like HN seems to consider worth reading, which is why I'm looking through the comments to this and others to find recommendations.
Don't give your code to Microsoft if you don't want them to have your code.
This setting will make no difference to whether your code is fed into their training set. "Oops we accidentally ignored the private flag years ago and didn't realise, we are very sorry, we were trying to not do that".
Currently, cuda to amdgpu. Product is at https://docs.scale-lang.com/stable/manual/how-to-install/, please email jon at spectralcompute.com if it misbehaves.
meet.hn/city/gb-Bristol
Socials: - github.com/JonChesterfield