From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com, cgen@sources.redhat.com
Cc: Nick Clifton <nickc@redhat.com>
Subject: iq2000 warning fix
Date: Fri, 19 Nov 2004 12:15:00 -0000 [thread overview]
Message-ID: <20041119121535.GB7749@bubble.modra.org> (raw)
This is an obvious patch to fix a warning, and of course needs applying
to the /src/cpu/ dir as well. It seems like /src/cpu/ is now supposed
to be the master, but I see the /src/cgen/cpu/ "copy" differs quite a
bit.. What's the story?
* cpu/iq2000.opc (parse_jtargq10): Change type of valuep to bfd_vma *.
Index: cgen/cpu/iq2000.opc
===================================================================
RCS file: /cvs/src/src/cgen/cpu/iq2000.opc,v
retrieving revision 1.2
diff -u -p -r1.2 iq2000.opc
--- cgen/cpu/iq2000.opc 14 Apr 2004 21:29:33 -0000 1.2
+++ cgen/cpu/iq2000.opc 19 Nov 2004 11:03:23 -0000
@@ -39,7 +39,7 @@ extern int iq2000_cgen_insn_supported (C
#include "safe-ctype.h"
static int iq2000_cgen_isa_register PARAMS ((const char **));
-static const char * parse_jtargq10 PARAMS ((CGEN_CPU_DESC, const char **, int, int, enum cgen_parse_operand_result *, unsigned long *));
+static const char * parse_jtargq10 PARAMS ((CGEN_CPU_DESC, const char **, int, int, enum cgen_parse_operand_result *, bfd_vma *));
static const char * parse_mimm PARAMS ((CGEN_CPU_DESC, const char **, int, long *));
static const char * parse_imm PARAMS ((CGEN_CPU_DESC, const char **, int, unsigned long *));
static const char * parse_hi16 PARAMS ((CGEN_CPU_DESC, const char **, int, unsigned long *));
@@ -156,7 +156,7 @@ parse_jtargq10 (cd, strp, opindex, reloc
int opindex;
int reloc ATTRIBUTE_UNUSED;
enum cgen_parse_operand_result *type_addr ATTRIBUTE_UNUSED;
- unsigned long *valuep;
+ bfd_vma *valuep;
{
const char *errmsg;
bfd_vma value;
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next reply other threads:[~2004-11-19 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 12:15 Alan Modra [this message]
2004-11-30 17:29 ` Nick Clifton
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=20041119121535.GB7749@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).