unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 9983@debbugs.gnu.org
Subject: bug#9983: valgrind warning in draw_glyphs
Date: Tue, 08 Nov 2011 09:17:08 -0500	[thread overview]
Message-ID: <yxq1utibswr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83vcqwhqnj.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Nov 2011 17:57:04 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Dan Nicolaescu <dann@gnu.org>,  9983@debbugs.gnu.org
>> Date: Mon, 07 Nov 2011 13:21:38 +0100
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > The other variables in the line being flagged, `start' and `i', are
>> > also okay: `start' is one of the call arguments
>> 
>> Just being an argument does not necessarily make it ok.
>
> Indeed.  I also thought about that, so I checked the callers two
> levels up, and came up empty-handed.
>
> I guess the optimization done by GCC 4.6 fooled valgrind as well.

Not trying to split hairs, but valgrind wasn't fooled, it did the right
thing at the level that valgrind is working at...





      reply	other threads:[~2011-11-08 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  4:36 bug#9983: valgrind warning in draw_glyphs Dan Nicolaescu
2011-11-07  5:49 ` Eli Zaretskii
2011-11-07 11:52   ` Dan Nicolaescu
2011-11-07 12:44     ` Dan Nicolaescu
2011-11-07 12:59       ` Andreas Schwab
2011-11-07 15:21         ` Dan Nicolaescu
2011-11-07 15:54         ` Eli Zaretskii
2011-11-07 12:21   ` Andreas Schwab
2011-11-07 15:57     ` Eli Zaretskii
2011-11-08 14:17       ` Dan Nicolaescu [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yxq1utibswr.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=9983@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).