From: Tom Tromey <tromey@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][testsuite] Add option to link testcases with pthreads when using 'prepare_for_testing'
Date: Mon, 15 Apr 2013 09:22:00 -0000 [thread overview]
Message-ID: <8761zrfox7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAGyQ6gyQ8+Txgam=W9+PCdFP1Uy_VHJrK3JM2pL=ZwpYVqjedA@mail.gmail.com> (Siva Chandra's message of "Sat, 23 Mar 2013 21:50:49 -0700")
>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:
Siva> The attached patch allows one to specify an option 'with_pthreads'
Siva> when using 'prepare_for_testing' in tests. One could call
Siva> gdb_compile_pthreads directly for such a purpose, but I think using
Siva> 'prepare_for_testing' is the suggested approach. If my understanding
Siva> or approach is wrong here, then what is the best way to make testcases
Siva> to link with pthreads for c++ testcases?
You can use gdb_compile_pthreads and put "c++" in the options.
However, I like your approach. Actually I wish most of the
gdb_compile_* procs would go away and be replaced by a variant of this
idea.
Siva> * lib/gdb.exp (build_executable_from_specs): Use
Siva> gdb_compile_pthreads to compile if option "with_pthreads" is
Siva> specified.
The intro comment to build_executable_from_specs needs an update to note
that with_pthreads is handled locally.
Siva> + if { [lsearch -exact $options "with_pthreads"] >= 0 } {
Siva> + if { [gdb_compile_pthreads $objects "${binfile}" executable $options] != "" } {
I wonder if you need to remove with_pthreads from the options here.
Tom
next prev parent reply other threads:[~2013-04-12 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 12:02 Siva Chandra
2013-04-15 9:22 ` Tom Tromey [this message]
2013-04-15 18:12 ` Siva Chandra
2013-04-15 18:51 ` Pedro Alves
2013-04-16 5:39 ` Siva Chandra
2013-04-16 5:47 ` Tom Tromey
2013-04-16 7:52 ` Siva Chandra
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=8761zrfox7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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