From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Subject: bfd warning fixes
Date: Thu, 17 Feb 2005 16:07:00 -0000 [thread overview]
Message-ID: <20050217123735.GY10128@bubble.modra.org> (raw)
Fixes gcc-4.0 fussing about possible use of an uninitialized struct
component.
bfd/
* elf-eh-frame.c (_bfd_elf_discard_section_eh_frame): Fix warning.
Index: bfd/elf-eh-frame.c
===================================================================
RCS file: /cvs/src/src/bfd/elf-eh-frame.c,v
retrieving revision 1.42
diff -u -p -r1.42 elf-eh-frame.c
--- bfd/elf-eh-frame.c 31 Jan 2005 20:39:08 -0000 1.42
+++ bfd/elf-eh-frame.c 17 Feb 2005 11:14:19 -0000
@@ -482,6 +482,7 @@ _bfd_elf_discard_section_eh_frame
on whether to output or discard last encountered CIE (if any). */
if ((bfd_size_type) (buf - ehbuf) == sec->size)
{
+ hdr.length = 0;
hdr.id = (unsigned int) -1;
end = buf;
}
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next reply other threads:[~2005-02-17 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 16:07 Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 11:57 Alan Modra
2000-07-09 22:22 Alan Modra
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=20050217123735.GY10128@bubble.modra.org \
--to=amodra@bigpond.net.au \
--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).