3 ms·
I have small experience with compilers and llvm but youd be shocked how many things rely on names and parsing names If you have hundreds of passes that are com
by high_na_euv 1y ago
I have small experience with compilers and llvm but youd be shocked how many things rely on names and parsing names
If you have hundreds of passes that are complex and rely on various "contracts" like type names or some shit, then really crazy things like this can happen unintentionally and not maliciously
- diggan 1y agoWeb-developers are well aware of this too. Sincerely, Mozilla/5.0 (X11; Linux x86_64; rv:139.0) Gecko/20100101 Firefox/139.0
- bravesoul2 1y agoFunny we send a browser wars tombstone in every request!
- antonvs 1y agoLet's have a moment of silence for Gecko/20100101
- halJordan 1y agoWhy would i be shocked that a name is informative. Like... are you surprised that wrought iron is wrought? Or cast iron is made from a cast?
- IAmBroom 1y agoDog piles are often neither composed of dogs, nor actual piles. Names can be both informative, and misdirecting, at the same time.
- the8472 1y agoSome names are standardized items, like memcpy. Matching those is ok, nothing sneaky going on there. Matching something vendor-specific in a general-purpose API is different story.