public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: binutils@sources.redhat.com
Subject: Fix compile time warning in cgen generated *-asm.c files
Date: Mon, 04 Apr 2005 10:09:00 -0000	[thread overview]
Message-ID: <m364z2c0u8.fsf@redhat.com> (raw)

Hi Guys,

  Alan pointed out that I had made a mistake in the opcodes directory,
  checking in a patch to the iq2000-asm.c file to fix a compile time
  warning without fixing the cgen file which was used to generate the
  iq2000-asm.c file.  Doh.

  So I am checking in the patch below to rectify this mistake.

Cheers
  Nick

cgen/ChangeLog
2005-04-04  Nick Clifton  <nickc@redhat.com>

	* opcodes.scm (-gen-parse-address): Initialise value to zero to
	avoid a compile time warning.

opcodes/ChangeLog
2005-04-04  Nick Clifton  <nickc@redhat.com>

	* fr30-asm.c: Regenerate.
	* frv-asm.c: Regenerate.
	* iq2000-asm.c: Regenerate.
	* m32r-asm.c: Regenerate.
	* openrisc-asm.c: Regenerate.

Index: cgen/opcodes.scm
===================================================================
RCS file: /cvs/src/src/cgen/opcodes.scm,v
retrieving revision 1.10
diff -c -3 -p -r1.10 opcodes.scm
*** cgen/opcodes.scm	23 Feb 2005 16:04:38 -0000	1.10
--- cgen/opcodes.scm	4 Apr 2005 09:09:37 -0000
***************
*** 355,361 ****
  (define (-gen-parse-address parse-fn op-enum result-var-name)
    (string-append
     "      {\n"
!    "        bfd_vma value;\n"
     "        errmsg = "
     ; Use operand's special parse function if there is one.
     (or parse-fn
--- 355,361 ----
  (define (-gen-parse-address parse-fn op-enum result-var-name)
    (string-append
     "      {\n"
!    "        bfd_vma value = 0;\n"
     "        errmsg = "
     ; Use operand's special parse function if there is one.
     (or parse-fn
  

                 reply	other threads:[~2005-04-04 10:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m364z2c0u8.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.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).