From: Ian Lance Taylor <ian@airs.com>
To: mark@codesourcery.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: PATCH for using both RELA and REL relocations in the samebackend
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990602042857.7489.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990601202858Z.mitchell@codesourcery.com>
From: Mark Mitchell <mark@codesourcery.com>
Date: Tue, 01 Jun 1999 20:28:58 -0700
@@ -3952,8 +3962,8 @@ swap_out_syms (abfd, sttp, relocatable_p
flagword flags = syms[idx]->flags;
int type;
- if (flags & BSF_SECTION_SYM)
- /* Section symbols have no names. */
+ if ((flags & BSF_SECTION_SYM) && !syms[idx]->name)
+ /* Some section symbols have no names. */
sym.st_name = 0;
else
{
By the way, this appears to be an unrelated patch. I believe this
will change gas behaviour on GNU/Linux and Solaris and other systems.
I'm not sure this is a good idea.
Ian
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Mark Mitchell
1999-07-01 0:00 ` Ian Lance Taylor [this message]
1999-07-01 0:00 ` Mark Mitchell
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Mark Mitchell
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=19990602042857.7489.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=mark@codesourcery.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).