From: Nick Clifton <nickc@redhat.com>
To: binutils@sources.redhat.com
Subject: Fix compile time warning in bfd/coff-tic4x.c
Date: Fri, 11 Feb 2005 18:45:00 -0000 [thread overview]
Message-ID: <m3wttf586u.fsf@redhat.com> (raw)
Hi Guys,
I am applying the patch below to fix a compile time warning building
bfd/coff-tic4x.c. This was actually a case where the warning proved
to be useful - there was an underlying bug that it picked up.
Cheers
Nick
bfd/ChangeLog
2005-02-11 Nick Clifton <nickc@redhat.com>
* coff-tic4x.c (coff_rtype_to_howto): Move definition before
inclusion of coffcode.h so that it is actually picked up.
Index: bfd/coff-tic4x.c
===================================================================
RCS file: /cvs/src/src/bfd/coff-tic4x.c,v
retrieving revision 1.8
diff -c -3 -p -r1.8 coff-tic4x.c
*** bfd/coff-tic4x.c 4 Jun 2003 11:38:30 -0000 1.8
--- bfd/coff-tic4x.c 11 Feb 2005 17:02:41 -0000
*************** ticoff_bfd_is_local_label_name (abfd, na
*** 68,73 ****
--- 68,77 ----
The COFF1 and COFF0 vectors use custom _bad_format_hook procs
instead of setting BADMAG. */
#define BADMAG(x) COFF2_BADMAG(x)
+
+ #undef coff_rtype_to_howto
+ #define coff_rtype_to_howto coff_tic4x_rtype_to_howto
+
#include "coffcode.h"
static bfd_reloc_status_type
*************** tic4x_lookup_howto (internal, dst)
*** 172,180 ****
abort();
}
- #undef coff_rtype_to_howto
- #define coff_rtype_to_howto coff_tic4x_rtype_to_howto
-
static reloc_howto_type *
coff_tic4x_rtype_to_howto (abfd, sec, rel, h, sym, addendp)
bfd *abfd ATTRIBUTE_UNUSED;
--- 176,181 ----
reply other threads:[~2005-02-11 17:05 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=m3wttf586u.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).