From: DJ Delorie <dj@redhat.com>
To: amodra@bigpond.net.au
Cc: binutils@sourceware.org
Subject: Re: [patch] am33 TLS support
Date: Fri, 12 May 2006 16:52:00 -0000 [thread overview]
Message-ID: <200605120214.k4C2EPka012127@greed.delorie.com> (raw)
In-Reply-To: <20060512020750.GA19700@bubble.grove.modra.org> (message from Alan Modra on Fri, 12 May 2006 11:37:50 +0930)
> The call won't be scheduled away from the other tls insn?
No. The GCC portion of the patch emits the whole group of insns in
one printf; the spec from MEI requires a specific opcode sequence.
prev parent reply other threads:[~2006-05-12 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 14:45 DJ Delorie
2006-05-12 15:07 ` Alan Modra
2006-05-12 16:52 ` DJ Delorie [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=200605120214.k4C2EPka012127@greed.delorie.com \
--to=dj@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
/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).