From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Subject: ld warning fix
Date: Thu, 17 Feb 2005 18:36:00 -0000 [thread overview]
Message-ID: <20050217130508.GB10128@bubble.modra.org> (raw)
gcc-4.0 is rather neat in that it can analyse whether aggregates are
all initialized or not.
* ldexp.c (new_abs): Init new.str.
Index: ld/ldexp.c
===================================================================
RCS file: /cvs/src/src/ld/ldexp.c,v
retrieving revision 1.42
diff -u -p -r1.42 ldexp.c
--- ld/ldexp.c 21 Jan 2005 04:15:58 -0000 1.42
+++ ld/ldexp.c 17 Feb 2005 11:15:32 -0000
@@ -144,6 +144,7 @@ new_abs (bfd_vma value)
new.valid_p = TRUE;
new.section = abs_output_section;
new.value = value;
+ new.str = NULL;
return new;
}
--
Alan Modra
IBM OzLabs - Linux Technology Centre
reply other threads:[~2005-02-17 13: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=20050217130508.GB10128@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).