Viewing profile — obl
obl
HN member- Joined
- Sun, Aug 09, 2015, 8:07 PM UTC
- HN karma
- 1,695
- Public activity
- 159 items
- HN profile
- View on Hacker News ↗
About obl
No profile information was provided.
Recent public activity
- story
-
comment
Comment #42460485
It is not ridiculous at all. Those things have pretty precise definitions and type segregation absolutely does remove a bunch of soundness issues related to type confusion. You can…
- story
- story
- story
-
comment
Comment #39194973
Weird that this treats uninitialized variables as unknown values. For example in ex3.c, the program int main(){ int x; if (x is of course UB in C, even though under a "uninitialize…
- story
- story
- story
- story
- story
- story
- story
-
comment
Comment #36358399
This is memory safe if you never re-use a (generational index, address) pair. They seem to use 64 bit ones so this means that to overflow a single memory cell you would have to all…
- story
- story
-
comment
Comment #35076792
Actual clipping is expensive so indeed a "guard band" is used : inside the region allowed by the internal precision of the rasterizer, outside pixels are simply "ignored". See e.g.…
-
comment
Comment #35076551
It would be interesting to see how you were testing for that, because at least on AMD it's fairly certain that a single thread can be shading multiple primitives. For example, from…
-
comment
Comment #35075116
In actual hardware shading is done 32 or 64 pixels at a time, not four. The problem above just got worse. While it's true that there are "wasted" execution in 2x2 quads for derivat…
- story
- story
- story
-
comment
Comment #33717362
If you didn't already, I'd recommend compiling llvm/clang in debug or release+assert mode when working on it. The codebase is quite heavy in debug-only assertions even for relative…
- story
- story