From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix MIPS bfd/elfxx-mips.c compile warning.
Date: Sat, 27 Aug 2005 23:15:00 -0000 [thread overview]
Message-ID: <4310F230.2030804@realitydiluted.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
Greetings.
This patch fixes a compile warning which gets turned into an
error and prevents cross building of gdb. It my be worthless,
but that's for you to decided.
-Steve
[-- Attachment #2: gdb-20050827-mips-cleanup.patch --]
[-- Type: text/x-patch, Size: 558 bytes --]
Index: elfxx-mips.c
===================================================================
RCS file: /cvs/src/src/bfd/elfxx-mips.c,v
retrieving revision 1.149
diff -u -r1.149 elfxx-mips.c
--- elfxx-mips.c 17 Aug 2005 10:04:26 -0000 1.149
+++ elfxx-mips.c 27 Aug 2005 23:04:41 -0000
@@ -6942,7 +6942,7 @@
for (rel = relocs; rel < relend; ++rel)
{
const char *name;
- bfd_vma value;
+ bfd_vma value = 0;
reloc_howto_type *howto;
bfd_boolean require_jalx;
/* TRUE if the relocation is a RELA relocation, rather than a
next reply other threads:[~2005-08-27 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 23:15 Steven J. Hill [this message]
2005-08-29 9:28 ` Daniel Jacobowitz
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=4310F230.2030804@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=gdb-patches@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