From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Microblaze simulator - Fix missing prototype
Date: Tue, 08 May 2012 05:21:00 -0000 [thread overview]
Message-ID: <m3wr4nmeo0.fsf@redhat.com> (raw)
In-Reply-To: <4FA82F46.4080901@oarcorp.com> (Joel Sherrill's message of "Mon, 7 May 2012 15:23:34 -0500")
Hi Joel,
Same comment from last e-mail: please send the patches to
gdb-patches@sourceware.org. I am replying this e-mail to the
appropriate list, with comments about your patch, but please send other
patches to that list.
On Monday, May 07 2012, Joel Sherrill wrote:
> Without this patch, this 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.
The `_initialize*' routines are treated specially by the Makefile, when
you build the project. They cannot be made static because they are
called from another source file. Take a look at gdb/Makefile.in, and
search for the rule `init.c:'.
> OK to apply?
Small nit below.
> Index: gdb/microblaze-rom.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/microblaze-rom.c,v
> retrieving revision 1.5
> diff -u -r1.5 microblaze-rom.c
> --- gdb/microblaze-rom.c 4 Jan 2012 08:17:06 -0000 1.5
> +++ gdb/microblaze-rom.c 7 May 2012 20:15:54 -0000
> @@ -25,6 +25,8 @@
> #include "serial.h"
> #include "regcache.h"
>
> +void _initialize_picobug_rom(void);
There should be a space between the function name and the open paren.
I am not a maintainer, but this change seems pretty trivial to me so
that it can be committed without an explicit approval.
Thanks,
--
Sergio
next parent reply other threads:[~2012-05-08 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FA82F46.4080901@oarcorp.com>
2012-05-08 5:21 ` Sergio Durigan Junior [this message]
2012-05-08 14:07 ` Joel Sherrill
2012-05-08 13:16 Joel Sherrill
2012-05-08 13:37 ` Mark Kettenis
2012-05-08 13:53 ` Sergio Durigan Junior
2012-05-15 13:30 ` Michael Eager
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=m3wr4nmeo0.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