Changes between Version 4 and Version 5 of PrimBool


Ignore:
Timestamp:
Jan 25, 2013 10:04:25 AM (3 years ago)
Author:
jstolarek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PrimBool

    v4 v5  
    2929}}}
    3030
    31 During the compilation process (assuming the optimizations are turned on) the definition of `(||)` gets inlined and then case-of-case transform is performed succesively. This results in following Core (cleaned up for clarity):
     31During the compilation process (assuming the optimizations are turned on) the definition of `(||)` gets inlined and then case-of-case transform is performed successively. This results in following Core (cleaned up for clarity):
    3232
    3333{{{
     
    7878}}}
    7979
    80 There are five possible branches to take, although four of them have the same result. This is caused by code duplication introduced by case-of-case transform. Mis-predicted branches are bad in object code because they stall the pipeline.
     80There are five possible branches to take, although four of them have the same result. This is caused by code duplication introduced by case-of-case transform. According to Ben Lippmeier, who submitted the original bug report, mis-predicted branches are bad in object code because they stall the pipeline.
    8181
    8282== Possible solutions and their consequences ==