[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-06-27 Thread ebotcazou at gcc dot gnu dot org
--- Comment #9 from ebotcazou at gcc dot gnu dot org 2010-06-27 08:27 --- Subject: Bug 43332 Author: ebotcazou Date: Sun Jun 27 08:27:39 2010 New Revision: 161459 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=161459 Log: Backport from mainline 2010-05-18

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-06-27 Thread ebotcazou at gcc dot gnu dot org
--- Comment #10 from ebotcazou at gcc dot gnu dot org 2010-06-27 08:31 --- Trivial fixes like this should be installed at the same time on branches. -- ebotcazou at gcc dot gnu dot org changed: What|Removed |Added

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-06-10 Thread zsojka at seznam dot cz
--- Comment #8 from zsojka at seznam dot cz 2010-06-10 15:45 --- Is there a chance this will be backported to 4.5? As Jakub pointed out at PR44178/comment #7, gcc 4.5 r160526 (with RTL checking) fails on this testcase with: $ gcc -fsched-pressure -fschedule-insns pr43332/testcase.c

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-06-09 Thread zsojka at seznam dot cz
--- Comment #7 from zsojka at seznam dot cz 2010-06-09 10:14 --- I have just finished bootstrap of r160198 with valgrind checking, the problem is no longer reproducible there. I am sorry for the delay, make check with valgrind checking takes about a month there (1.3GHz), bootstrap about

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-05-18 Thread vmakarov at redhat dot com
--- Comment #4 from vmakarov at redhat dot com 2010-05-18 21:40 --- Thanks for reporting the problem. The problem has no effect on generated code whatever initialization is used. The code in question tries to get basic block for BARRIER which is wrong. Whatever it gets basic block

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-05-18 Thread vmakarov at gcc dot gnu dot org
--- Comment #5 from vmakarov at gcc dot gnu dot org 2010-05-18 22:09 --- Subject: Bug 43332 Author: vmakarov Date: Tue May 18 22:09:19 2010 New Revision: 159545 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=159545 Log: 2010-05-18 Vladimir Makarov vmaka...@redhat.com

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-05-18 Thread zsojka at seznam dot cz
--- Comment #6 from zsojka at seznam dot cz 2010-05-18 22:22 --- Thank you for fixing this. I hope to rebuild gcc with valgrind checking in few days again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43332

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-05-17 Thread zsojka at seznam dot cz
--- Comment #3 from zsojka at seznam dot cz 2010-05-17 18:45 --- Stil appears in r159500, x86_64-linux. Uninitialised read is at gcc/haifa-sched.c:1589, more exactly it is read of BLOCK_FOR_INSN (insn) When gcc/haifa-sched.c:1589 is changed to: insn != NULL_RTX (printf(%p %p\n, (void

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-03-13 Thread zsojka at seznam dot cz
--- Comment #2 from zsojka at seznam dot cz 2010-03-13 09:19 --- Thank you for feedback. However, this happens in r157335, so it's not fixed by that patch. It's only reproducible with valgrind checking because ggc_alloc_stat() uses VALGRIND_DISCARD which is a no-op in other cases. When

[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns

2010-03-12 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2010-03-13 02:51 --- It is the same and was fixed by the same patch. *** This bug has been marked as a duplicate of 42941 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added