Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ha! This is actually pretty darn clever!

I wonder what the final binary sizes are in comparison to normal GCC compilation, as well as execution speed.

I can't believe you made a floating point emulator just for this as well! Quite impressed.



Considering that the floating point library is big enough to be disabled by default tells me you might run out of disk space compiling a single application.

That being said, if this can increase difficulty of sidechannel attacks and branch prediction, maybe it'd actually make sense for very isolated parts of some services.


>That being said, if this can increase difficulty of sidechannel attacks and branch prediction, maybe it'd actually make sense for very isolated parts of some services.

I agree, I can see how it certain special circumstances/services this could be very useful.

However, I still expect someone to compile Quake with it by the end of the year.


They've apparently done DOOM already, and it's hours per frame. I don't want to think what Quake would be like.


To be clear, I (the HN submitter) have nothing to do with this, I just found it and thought it was great.


From the example images of original and obfuscated assembly, there's seems to be about a sixfold increase in the number of instructions (for that example, at least), so I imagine you'll see a similar binary size increase.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: