From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, i386]: Cleanup TARGET_GNU2_TLS usage
Date: Wed, 18 May 2011 15:28:00 -0000 [thread overview]
Message-ID: <yddmxik2qlc.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <BANLkTikEFxtptQv-pgO5NSd1eKVjJ_CcJQ@mail.gmail.com> (Uros Bizjak's message of "Wed, 11 May 2011 17:42:40 +0200")
Uros,
> The test (tls.c), used to check all TLS models is attached to the
> message. I plan to convert it to proper dg test... ;)
I've got it in my tree since you sent it to me while debugging/testing
support for the various TLS models on Solaris. I'd really prefer (and
have modified it this way) the test to be split into one test per access
model so it becomes easier to figure out what is failing.
I can provide such a patch if desired.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-05-18 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:28 Uros Bizjak
2011-05-18 15:28 ` Rainer Orth [this message]
2011-05-18 15:53 ` Uros Bizjak
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=yddmxik2qlc.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.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).