http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55309
--- Comment #10 from Kostya Serebryany <kcc at gcc dot gnu.org> 2013-02-05
10:41:20 UTC ---
(In reply to comment #8)
> "464.h264ref with gcc loops forever, I did not investigate why."
> is PR53073 , you can use -fno-aggressive-loop-optimizations to workaround the
> invalid code in SPEC.
Thanks. But then again we hit another bug in 464.h264ref.
So, if we want to run h264ref and perbmk w/o changing sources under gcc+asan
we need to have the blacklist functionality.
(see the same links as above).
==8720== ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7fff625736a0 at pc 0x4e2a98 bp 0x7fff62573600 sp 0x7fff625735f8
READ of size 4 at 0x7fff625736a0 thread T0
#0 0x4e2a97 in SATD
(benchspec/CPU2006/464.h264ref/run/run_base_ref_z.0000/h264ref_base.z+0x4e2a97)
#1 0x4e47c0 in SubPelBlockMotionSearch
(benchspec/CPU2006/464.h264ref/run/run_base_ref_z.0000/h264ref_base.z+0x4e47c0)
...
Address 0x7fff625736a0 is located at offset 96 in frame <SATD> of T0's stack:
This frame has 1 object(s):
[32, 96) 'd'
