4 ms·
I work with compilers And despite it not being nice, some optimizations rely on type or function names schemas/substrings/etc It sucks, but thats how it works
by high_na_euv 1y ago
I work with compilers
And despite it not being nice, some optimizations rely on type or function names schemas/substrings/etc
It sucks, but thats how it works
It doesnt have to be malicious just sometimes it is safer to deploy optimization only for your libs than risk breaking stuff
Or your frontend is not giving you more data which you can rely on
- tliltocatl 1y agoIt is probably not malicious, but it certainly does create new barriers, which is not a good thing.
- Hizonner 1y ago> than risk breaking stuff ... until somebody randomly chooses the same name for some reason and gets hosed. You're not helping.
- wiz21c 1y agoOn function types or schema, I can understand that. But names ?
- mhh__ 1y agoSomething like: if(AskLLM("Does function signature+name look like error handling code")) { TurnOffInliner(); } is actually probably a lot more effective than you'd think (generating PGO traces with a machine learning tool is apparently a thing that sort of works)
- colejohnson66 1y agoNot exactly the same, but intrinsics in some languages are purely name+signature matched.
- high_na_euv 1y agoSure, but will anyone name a method like "__nvidia_experimental_feature_xyz_v1"?
- high_na_euv 1y agoYes. E.g "__nvidia_experimental_feature_xyz_v1"