public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns
Date: Tue, 18 May 2010 21:40:00 -0000 [thread overview]
Message-ID: <20100518214019.18253.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43332-14164@http.gcc.gnu.org/bugzilla/>
------- 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 for BARRIER the
code will still work right.
In any case, it is really annoying to see such valgrind diagnostic.
Therefore I'll send a patch to fix it soon.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43332
next prev parent reply other threads:[~2010-05-18 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 15:11 [Bug rtl-optimization/43332] New: " zsojka at seznam dot cz
2010-03-13 2:52 ` [Bug rtl-optimization/43332] " pinskia at gcc dot gnu dot org
2010-03-13 9:20 ` zsojka at seznam dot cz
2010-05-17 18:46 ` zsojka at seznam dot cz
2010-05-18 21:40 ` vmakarov at redhat dot com [this message]
2010-05-18 22:09 ` vmakarov at gcc dot gnu dot org
2010-05-18 22:22 ` zsojka at seznam dot cz
2010-06-09 10:15 ` zsojka at seznam dot cz
2010-06-10 15:45 ` zsojka at seznam dot cz
2010-06-27 8:28 ` ebotcazou at gcc dot gnu dot org
2010-06-27 8:31 ` ebotcazou at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100518214019.18253.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).