Re: [pypy-svn] r23599 - pypy/dist/pypy/translator/c/src
H, I have a local version that does the test for the 'errorvalue' that gets returned when stack unwinding is going on. I did not check this in yet because it did not give a speedup, I will keep it around and look into a little further. We probably are making life difficult for the compiler because of the use of the resume_label. What we IMO really should to do is tell the compiler not to bother with the label and let all the register setup be handled in the resume block. In other words we need to make it clearer (for the compiler) that non stack unwind/resume is the case to optimize. Now the question is of course, how to do that? cheers Eric On Feb 22, 2006, at 9:22 PM, tismer@codespeak.net wrote:
HI, Sorry for replying to my own mail, but I will have a look into the gcc option -fprofile-arcs to aid branch prediction and maybe also experiment with __builtin_expect(...) to tell gcc that exception are not the common case. (sound logical doesn't?) . I take it similar options exist for other compilers, but that's another story... cheers Eric On Feb 22, 2006, at 10:43 PM, Eric van Riet Paap wrote:
HI, Sorry for replying to my own mail, but I will have a look into the gcc option -fprofile-arcs to aid branch prediction and maybe also experiment with __builtin_expect(...) to tell gcc that exception are not the common case. (sound logical doesn't?) . I take it similar options exist for other compilers, but that's another story... cheers Eric On Feb 22, 2006, at 10:43 PM, Eric van Riet Paap wrote:
participants (1)
-
Eric van Riet Paap