Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday November 02 2015, @04:31AM   Printer-friendly
from the next-up:-jump-jiving dept.

The "jump threading" compiler optimization (aka -fthread-jump) turns conditional into unconditional branches on certain paths at the expense of code size. For hardware with branch prediction, speculative execution, and prefetching, this can greatly improve performance. However, there is no scientific publication or documentation at all. The Wikipedia article is very short and incomplete.

The linked article has an illustrated treatment of common code structures and how these optimizations work.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by gnuman on Tuesday November 03 2015, @05:18AM

    by gnuman (5013) on Tuesday November 03 2015, @05:18AM (#257823)

    Crazy, I know.

    It's called code style or coding guidelines. Especially with C, you need to follow it or you get yourself in trouble.

    And there is nothing wrong with this code style. Compilers easily optimize it removing the goto, but it's actually easier to understand for humans. Successful return statement in ONE place.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2