public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/54783] [4.8 Regression] valgrind reports using uninitialised data in mark_pseudo_regno_live and make_object_born on basic code
Date: Wed, 03 Oct 2012 06:54:00 -0000	[thread overview]
Message-ID: <bug-54783-4-ZpK9zNUx87@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54783-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54783

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-03 06:54:22 UTC ---
Alternative would be to check for valgrind devel headers always, tweak the
existing VALGRIND* macros used in gcc sources such that it would be only used
if ENABLE_VALGRIND_CHECKING (otherwise expand to nothing) and in sparseset for
hosts that have valgrind support, but no valgrind devel headers, fall back to
XCNEWVEC, otherwise if valgrind devel headers are available, use the valgrind
special insn even without --enable-checking=valgrind.


  parent reply	other threads:[~2012-10-03  6:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 19:56 [Bug rtl-optimization/54783] New: " zsojka at seznam dot cz
2012-10-03  6:34 ` [Bug rtl-optimization/54783] " mpolacek at gcc dot gnu.org
2012-10-03  6:54 ` jakub at gcc dot gnu.org [this message]
2012-10-04 12:18 ` rguenth at gcc dot gnu.org
2012-11-13  7:29 ` jakub at gcc dot gnu.org
2012-12-07 11:46 ` rguenth at gcc dot gnu.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=bug-54783-4-ZpK9zNUx87@http.gcc.gnu.org/bugzilla/ \
    --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).