work log

• Optimization threads use polling to probe tasks in task queue.
• It uses 17% CPU just polling empty task queue continuously.
• Should change to conditional wait approach!
• 456.hmmer is trapped in a infinite loop when running in trace mode.
• Is it because of traces? Or it is due to the ``O0'' compiled code?
• Just execution ``O0'' in block mode, hmmer can successfully complete.
• So, it is traces' fault!!! NOT GOOD!
• Status of trace mode:
• 401.bzip2: OK, 142s
• 403.gcc: OK, 416s
• 429.mcf: OK, 56s
• 445.gobmk: OK, 804s
• 456.hmmer, NOT OK, infinite loop
• Due to generated traces.
• 458.sjeng          --      116           -- S
• 462.libquantum     --       14.0         -- S
• 464.h264ref        --      256              RE (SegFault)
• 473.astar          --      100           -- S
• 483.xalancbmk      --      171           -- S
• Debug 456.hmmer
• Check MI used by traces and compared with those used in blocks.
• Fail! they are the same
• will debuggingix h264ref be slightly easier?