From: Tom Tromey <tromey@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Will Newton <will.newton@linaro.org>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH] gdb/testsuite/gdb.threads: Make sure TLS tests link against pthreads.
Date: Wed, 17 Jul 2013 18:16:00 -0000 [thread overview]
Message-ID: <87mwplf3xn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CA+=Sn1=K2QkVFW0J7=_dimQ57GgeP44AmrNYqakNDDybL83-Sg@mail.gmail.com> (Andrew Pinski's message of "Tue, 11 Jun 2013 16:02:34 -0700")
Andrew> I think this should be an debian/Ubuntu local only patch as the
Andrew> default for FSF GCC/binutils is not to pass --as-needed.
If that is the only reason, then I think it is still ok in principle to
use the patch. It won't hurt the FSF default case.
Tom
next prev parent reply other threads:[~2013-07-17 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 18:41 Will Newton
2013-06-11 23:39 ` Andrew Pinski
2013-06-12 10:26 ` Will Newton
2013-06-12 11:57 ` Joel Brobecker
2013-07-17 18:16 ` Tom Tromey [this message]
2013-07-17 18:18 ` Tom Tromey
2013-07-17 19:05 ` Mark Kettenis
2013-07-17 20:17 ` Will Newton
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=87mwplf3xn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patches@linaro.org \
--cc=pinskia@gmail.com \
--cc=will.newton@linaro.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