From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: sim/erc32 warnings
Date: Fri, 07 Nov 2008 17:25:00 -0000 [thread overview]
Message-ID: <491479EC.3070907@oarcorp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hi,
I am working through the RTEMS gdb patch
and submitting it in pieces.
erc32.c needed to include string.h and
get rid of symbols after endif.
exec.c had a ";" where some gcc versions
wanted a "break;"
2008-11-07 Joel Sherrill <joel.sherrill@oarcorp.com>
* erc32.c, exec.c: Fix warnings.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
[-- Attachment #2: sis-warnings.diff --]
[-- Type: text/x-patch, Size: 810 bytes --]
? .exec.c.swp
Index: erc32.c
===================================================================
RCS file: /cvs/src/src/sim/erc32/erc32.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 erc32.c
--- erc32.c 16 Apr 1999 01:35:00 -0000 1.1.1.1
+++ erc32.c 7 Nov 2008 17:21:50 -0000
@@ -24,6 +24,7 @@
#include <sys/types.h>
#include <stdio.h>
+#include <string.h>
#include <termios.h>
#include <sys/fcntl.h>
#include <sys/file.h>
@@ -1659,7 +1660,7 @@
errmec = 0;
return(1);
}
-#endif;
+#endif
if ((addr >= mem_ramstart) && (addr < (mem_ramstart + mem_ramsz))) {
fetch_bytes (asi, &ramb[addr & mem_rammask], data, sz);
@@ -1736,7 +1737,7 @@
errmec = 0;
return(1);
}
-#endif;
+#endif
if ((addr >= mem_ramstart) && (addr < (mem_ramstart + mem_ramsz))) {
if (mem_accprot) {
next reply other threads:[~2008-11-07 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 17:25 Joel Sherrill [this message]
2008-11-08 1:27 ` Hans-Peter Nilsson
2008-11-11 23:12 ` 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=491479EC.3070907@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb-patches@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