public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/18091] Valgrind errors building libjava
Date: Wed, 20 Oct 2004 20:49:00 -0000	[thread overview]
Message-ID: <20041020204915.14740.qmail@sourceware.org> (raw)
In-Reply-To: <20041020200437.18091.drow@gcc.gnu.org>


------- Additional Comments From mckinlay at redhat dot com  2004-10-20 20:49 -------
For the memcpy() thing, in the error given we seem to be relocating something to
the exact same position. In this case the memcpy() should be harmless. But,
maybe it is possible to get real overlapping relocations. Its probably best just
to replace the memcpy() with a memmove() here.

I'm not sure the "unitialized conditional move" errors are really bugs. I've
seen this a bit when running valgrind on code compiled with recent GCCs ?


-- 


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


  parent reply	other threads:[~2004-10-20 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 20:04 [Bug java/18091] New: " drow at gcc dot gnu dot org
2004-10-20 20:24 ` [Bug java/18091] " pinskia at gcc dot gnu dot org
2004-10-20 20:27 ` pinskia at gcc dot gnu dot org
2004-10-20 20:49 ` mckinlay at redhat dot com [this message]
2004-10-20 21:04 ` pinskia at gcc dot gnu dot org
2004-10-21 14:38 ` cvs-commit at gcc dot gnu dot org
2004-12-16 14:29 ` aph at gcc dot gnu dot org
2005-01-03 22:25 ` pinskia at gcc dot gnu dot org
2005-01-21  2:38 ` cvs-commit at gcc dot gnu dot org
2005-01-21  2:39 ` tromey at gcc dot gnu dot org
2005-01-21  2:40 ` pinskia 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=20041020204915.14740.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).