From: Bob Wilson <bwilson@tensilica.com>
To: binutils@sources.redhat.com
Subject: Re: fix Xtensa property tables with relaxation and --gc-sections
Date: Fri, 27 Apr 2007 19:46:00 -0000 [thread overview]
Message-ID: <463241B0.9020002@tensilica.com> (raw)
In-Reply-To: <461E827B.7090907@tensilica.com>
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
Oops. My previous patch had an extra increment, so it skipped over every other
relocation. I've committed this patch to fix it.
bfd/
* elf32-xtensa.c (relax_property_section): Remove extra irel increment.
[-- Attachment #2: bfd-extra-inc.patch --]
[-- Type: text/x-diff, Size: 399 bytes --]
Index: elf32-xtensa.c
===================================================================
RCS file: /cvs/src/src/bfd/elf32-xtensa.c,v
retrieving revision 1.86
diff -u -r1.86 elf32-xtensa.c
--- elf32-xtensa.c 26 Apr 2007 14:46:57 -0000 1.86
+++ elf32-xtensa.c 27 Apr 2007 18:27:18 -0000
@@ -9037,7 +9037,6 @@
break;
}
irel->r_offset -= removed_bytes;
- irel++;
}
}
prev parent reply other threads:[~2007-04-27 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 19:13 Bob Wilson
2007-04-27 19:46 ` Bob Wilson [this message]
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=463241B0.9020002@tensilica.com \
--to=bwilson@tensilica.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).