public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: msnyder@sonic.net
To: binutils@sourceware.org
Subject: Re: [PATCH] elf.c, remove effectless increment
Date: Thu, 26 Jul 2007 18:18:00 -0000	[thread overview]
Message-ID: <17521.12.7.175.2.1185473786.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <20070726062722.GB11649@bubble.grove.modra.org>

> On Wed, Jul 25, 2007 at 02:23:03PM -0700, msnyder@sonic.net wrote:
>> No point incrementing the pointer 's', which is
>>   a) uninitialized
>>   b) not used in the loop, and
>>   c) assigned to right after the loop.
>>
>
>> 2007-07-25  Michael Snyder  <msnyder@access-company.com>
>>
>> 	* elf.c (_bfd_elf_get_synthetic_symtab): Remove meaningless
>> 	pointer increment.
>
> OK.

Thanks, committed.


      reply	other threads:[~2007-07-26 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 21:26 msnyder
2007-07-26  6:27 ` Alan Modra
2007-07-26 18:18   ` msnyder [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

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

  git send-email \
    --in-reply-to=17521.12.7.175.2.1185473786.squirrel@webmail.sonic.net \
    --to=msnyder@sonic.net \
    --cc=binutils@sourceware.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).