search for: llvm_patch

I don't believe the changes have made it in yet. In addition to the previous patch set, we've got an independent implementation we've been using for a while: https://github.com/AzulSystems/llvm-late-safepoint-placement We really should get one or the other merged in tree. Could you point me to the previous patch set so I can ping it and review? Philip -------- Original Message

...would have to accept that there might be extra registers that are included unnecessarily (which can already happen). I created a hacky little patch that simply ignores bogus registers when doing the liveness calculation: https://github.com/kmod/pyston/blob/73a1a9897ec649f2249a69d523c820c0d4321786/llvm_patches/0009-Filter-out-extraneous-registers-from-live-outs-like-.patch Not sure if this is the kind of approach we would like to go with, but so far in my very limited testing it seems to be ok and at least things don't crash. What do you guys think? kmod -------------- next part -------------- An...

...at there might be extra registers that are included unnecessarily > (which can already happen). > > I created a hacky little patch that simply ignores bogus registers when > doing the liveness calculation: > https://github.com/kmod/pyston/blob/73a1a9897ec649f2249a69d523c820c0d4321786/llvm_patches/0009-Filter-out-extraneous-registers-from-live-outs-like-.patch > Not sure if this is the kind of approach we would like to go with, but so > far in my very limited testing it seems to be ok and at least things don't > crash. What do you guys think? > > > The %RIP problem i...

I want to run a bunch of optimizations, iteratively, that is keep running until things stop changing (to make sure all optimization opportunities are taken). As far as I know, there is no way to copy a module or compare modules by value, so it occurs to me that a practical solution might be to take the hash code of the module and see if that changes. A problem is that hash algorithms are designed