Hello, sorry for the late answer.
> Vlad promised to update it to use df.c once it wasn't "1% slower", which > would make it easily reusable elsewhere, but never did. > Of course, you could reuse it without that, but then someone will > invariably come along and mess with it. Ok I understand that implementing the special lifeness analyzers in global alloc using the df.c framework would ease reusing it somewhere else. But my question was more basic. So do you agree that using one lifeness analyzer for checking what an optimizer step has done based on a second lifeness analyzers output is wrong? If so what is the way to fix this? Going back to the normal analyzer to be used in global alloc would make global alloc creating worse code. But on the other hand using the global alloc lifeness analyzer everywhere else would be a change which nobody would agree with in the current development stage. Because this is a regression from 4.0 to 4.1 this should be fixed as soon as possible. Bye, -Andreas-
