Jack Doerner
Jack Doerner
I just ran into this one while trying to build my library on an updated system for the first time. For now, what's the suggested mitigation? #undef __HAVE_DISTINCT_FLOAT128? If that's...
I am already compiling with --std=c99, and it doesn't seem to help, unfortunately.
No, do you need someone to verify that it works? I've been using `-D _Float128=double` per @schoppmp. WRT the patch, it looks like the right idea, but it seems like...
Oh, hey, you're right. I misread that I guess. I'll give it a try sometime soon and report. As an additional thought: there is a similar-but-not-necessarily-identical problem with 128-bit integer...
I'm realizing only now that I never notified you: I believe your concerns have been taken care of. I will handle all of the other issues we talked about in...
Btw, I still have two other largish PRs to submit after this one. Any chance we can get it merged before too long?
RE: Previous comment chain, for the record: > > when you consider code that uses many threads over its lifetime, but each only for a short duration >That's just bad...
My understanding of line 676 in `obliv_bits.c`: `for(i=0;i8*i)&0xff);` Is that you're filling a 128 bit buffer with two copies of the 64 bit gate count. The simple way would seem...
Ahh, thanks for the clarification. My logic should still hold, yes? I assume that the higher half of the counter is always 0 as currently coded? If so, we could...
> It should work. How do you plan to do this? Pretty much just as you described, I think. A cap sounds reasonable, as long as we have a way...