seen with a profiled build (make profile-opt
PROFILE_TASK='$(srcdir)/Lib/test/regrtest.py') building python-3.0rc3 on
i486-linux-gnu. Using pybench as the PROFILE_TASK doesn't show this bug). Seen
PR22471, but this one was reported long ago. What other information should be
provided for this kind of report?
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes
-fprofile-use -I. -IInclude -I../Include -DPy_BUILD_CORE -o Modules/config.o
Modules/config.c
../Python/thread.c: In function 'PyThread_acquire_lock':
../Python/thread.c:419: error: corrupted profile info: number of executions for
edge 16-3 thought to be -1
../Python/thread.c:419: error: corrupted profile info: number of executions for
edge 16-17 thought to be 5657524
make[3]: *** [Python/thread.o] Error 1
--
Summary: corrupted profile info with -O[23] -fprofile-use
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: doko at ubuntu dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38292
