From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [testsuite] Pass -lpthread in libs
Date: Wed, 22 Nov 2017 15:30:00 -0000 [thread overview]
Message-ID: <ba3fa9e0055eec3b35f8ed62832e24f4@polymtl.ca> (raw)
In-Reply-To: <868teys5q7.fsf@gmail.com>
On 2017-11-22 10:17, Yao Qi wrote:
> Simon Marchi <simon.marchi@ericsson.com> writes:
>
>> I am seeing:
>>
>> gdb compile failed, .../info-os.c:51:1: warning: control reaches end
>> of non-void function [-Wreturn-type]
>>
>> with clang-6.0. Once I fix it, the test passes for me.
>
> Yes, it is another patch in my tree, to be posted.
>
>>
>> Instead of passing -lpthread directly, it would probably be better to
>> pass the
>> "pthreads" option, like this:
>
> OK, how about the patch below?
>
> --
> Yao (é½å°§)
>
> From c7392e6f937bf342daee99dfd5bcc6daf91af417 Mon Sep 17 00:00:00 2001
> From: Yao Qi <yao.qi@linaro.org>
> Date: Fri, 17 Nov 2017 13:04:10 +0000
> Subject: [PATCH] [testsuite] Pass pthreads in prepare_for_testing
>
> "pthreads" in the right flag to pass in prepare_for_testing to linker,
> instead of additional_flags. Without this patch, the test case can't
> be
> complied by clang.
>
> gdb compile failed, clang: warning: -lpthread: 'linker' input unused
>
> gdb/testsuite:
>
> 2017-11-22 Yao Qi <yao.qi@linaro.org>
>
> * gdb.base/info-os.exp: Pass pthreads.
> * gdb.multi/multi-attach.exp: Likewise.
>
> diff --git a/gdb/testsuite/gdb.base/info-os.exp
> b/gdb/testsuite/gdb.base/info-os.exp
> index 574da26..3267eec 100644
> --- a/gdb/testsuite/gdb.base/info-os.exp
> +++ b/gdb/testsuite/gdb.base/info-os.exp
> @@ -28,7 +28,7 @@ if [gdb_skip_xml_test] then {
> }
>
> # Compile test program.
> -if { [prepare_for_testing "failed to prepare" $testfile $srcfile
> {debug additional_flags=-lpthread}] } {
> +if { [prepare_for_testing "failed to prepare" $testfile $srcfile
> {debug pthreads}] } {
> fail "cannot compile test program"
> return -1
> }
> diff --git a/gdb/testsuite/gdb.multi/multi-attach.exp
> b/gdb/testsuite/gdb.multi/multi-attach.exp
> index 9397f85..0e54b4f 100644
> --- a/gdb/testsuite/gdb.multi/multi-attach.exp
> +++ b/gdb/testsuite/gdb.multi/multi-attach.exp
> @@ -23,7 +23,7 @@ if {![can_spawn_for_attach]} {
> return 0
> }
>
> -if {[prepare_for_testing "failed to prepare" $testfile $srcfile
> {debug additional_flags=-lpthread}]} {
> +if {[prepare_for_testing "failed to prepare" $testfile $srcfile
> {debug pthreads}]} {
> return -1
> }
LGTM.
next prev parent reply other threads:[~2017-11-22 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 15:22 Yao Qi
2017-11-17 16:54 ` Simon Marchi
2017-11-22 15:17 ` Yao Qi
2017-11-22 15:30 ` Simon Marchi [this message]
2017-11-22 16:52 ` Yao Qi
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=ba3fa9e0055eec3b35f8ed62832e24f4@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=simon.marchi@ericsson.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