From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: thomas@codesourcery.com
Cc: binutils@sourceware.org
Subject: Re: [SH] TLS IE -> LE optimization issue
Date: Tue, 17 Apr 2012 22:13:00 -0000 [thread overview]
Message-ID: <20120418.070301.283176808.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <20120417.231222.133469554.kkojima@rr.iij4u.or.jp>
> Thanks for testing. I'll apply it as a quick fix.
For the record, I've committed it with the entry below:
2012-04-17 Kaz Kojima <kkojima@rr.iij4u.or.jp>
* elf32-sh.c (allocate_dynrelocs): Don't allocate dynamic
relocations when LE conversion happens on the IE tls symbol.
Regards,
kaz
prev parent reply other threads:[~2012-04-17 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 15:53 Thomas Schwinge
2012-04-13 15:55 ` David Miller
2012-04-14 0:27 ` Kaz Kojima
2012-04-15 22:18 ` Alan Modra
2012-04-16 11:47 ` Kaz Kojima
2012-04-17 12:36 ` Thomas Schwinge
2012-04-17 14:48 ` Kaz Kojima
2012-04-17 22:13 ` Kaz Kojima [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=20120418.070301.283176808.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=binutils@sourceware.org \
--cc=thomas@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).