From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Microblaze simulator - Fix missing prototype
Date: Tue, 08 May 2012 13:53:00 -0000 [thread overview]
Message-ID: <m37gwmn5is.fsf@redhat.com> (raw)
In-Reply-To: <4FA91C76.1090108@oarcorp.com> (Joel Sherrill's message of "Tue, 8 May 2012 08:15:34 -0500")
On Tuesday, May 08 2012, Joel Sherrill wrote:
> Without this patch, the Microblaze simulator generates
> a missing prototype warning which is treated as an error.
> I don't see this routine referenced elsewhere, so there is
> the possibility that it also could be made static. But
> it definitely needs a prototype to build.
(a) The patch does not reflect the subject of the message, nor the
ChangeLog;
(b) I have already made comments about the message above in
http://sourceware.org/ml/gdb-patches/2012-05/msg00207.html
--
Sergio
next prev parent reply other threads:[~2012-05-08 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:16 Joel Sherrill
2012-05-08 13:37 ` Mark Kettenis
2012-05-08 13:53 ` Sergio Durigan Junior [this message]
2012-05-15 13:30 ` Michael Eager
[not found] <4FA82F46.4080901@oarcorp.com>
2012-05-08 5:21 ` Sergio Durigan Junior
2012-05-08 14:07 ` Joel Sherrill
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=m37gwmn5is.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=joel.sherrill@oarcorp.com \
/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