public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/8] Add configure check for std::thread
Date: Thu, 30 May 2019 11:34:00 -0000	[thread overview]
Message-ID: <04acc58e-d293-1753-a106-15b94c5d5cbf@redhat.com> (raw)
In-Reply-To: <20190529212916.23721-4-tom@tromey.com>

On 5/29/19 10:29 PM, Tom Tromey wrote:
> This adds a configure check for std::thread.  This is needed because
> std::thread is not available in mingw.

AFAICT, the patch actually does two things:

- Add autoconf bits (ax_pthread.m4) to make sure we build with the
  right -pthread, -pthreads, -lpthread, -lpthreads, or whatever the
  right spelling is on the host to pull in the pthreads library.

- Adds a configure check for std::thread, since it is not available
  on some platforms, at least out of the box.  I think mingw-w64
  (but not mingw.org) supports std::thread OOTB nowadays.  I'd guess
  that DJGPP doesn't support it either, at least OOTB.  Googling around
  seems to confirm that.

Right?

It'll be good to extend the commit log in that direction, IMO.

On 5/29/19 10:29 PM, Tom Tromey wrote:

>  $(srcdir)/aclocal.m4: @MAINTAINER_MODE_TRUE@ $(aclocal_m4_deps)
>  	cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
> diff --git a/gdb/acinclude.m4 b/gdb/acinclude.m4
> index 0719d422a71..ff463ea3595 100644
> --- a/gdb/acinclude.m4
> +++ b/gdb/acinclude.m4
> @@ -76,6 +76,8 @@ m4_include(ptrace.m4)
>  
>  m4_include(ax_cxx_compile_stdcxx.m4)
>  
> +sinclude([../config/ax_pthread.m4])

Is there reason to prefer sinclude over m4_include?  I never
got why we use sinclude so frequently, given it doesn't error
out if the file doesn't exist.

> --- a/gdb/common/common.m4
> +++ b/gdb/common/common.m4
> @@ -35,6 +35,31 @@ AC_DEFUN([GDB_AC_COMMON], [
>  
>    AC_CHECK_DECLS([strerror, strstr])
>  
> +  # Check for std::thread.  This does not work on mingw.

Maybe mention DJGPP too.

> +  AC_LANG_PUSH([C++])
> +  AX_PTHREAD([threads=yes], [threads=no])
> +  if test "$threads" = "yes"; then
> +    save_LIBS="$LIBS"
> +    LIBS="$PTHREAD_LIBS $LIBS"
> +    save_CXXFLAGS="$CXXFLAGS"
> +    CXXFLAGS="$PTHREAD_CFLAGS $save_CFLAGS"

I think you meant save_CXXFLAGS here.

Otherwise looks fine to me.

Thanks,
Pedro Alves

  reply	other threads:[~2019-05-30 11:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 21:29 [PATCH v3 0/8] Demangle minimal symbol names in worker threads Tom Tromey
2019-05-29 21:29 ` [PATCH v3 8/8] Add maint set/show max-worker-threads Tom Tromey
2019-05-30  2:36   ` Eli Zaretskii
2019-05-30 14:20   ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 4/8] Lock the demangled hash table Tom Tromey
2019-05-30 12:58   ` Pedro Alves
2019-05-30 14:03     ` Pedro Alves
2019-05-30 21:58     ` Tom Tromey
2019-05-29 21:29 ` [PATCH v3 1/8] Defer minimal symbol name-setting Tom Tromey
2019-05-29 21:29 ` [PATCH v3 2/8] Remove static buffer from ada_decode Tom Tromey
2019-05-30  0:08   ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 5/8] Introduce run_on_main_thread Tom Tromey
2019-05-30 13:12   ` Pedro Alves
2019-05-30 13:20     ` Tom Tromey
2019-05-30 13:57       ` Pedro Alves
2019-05-30 14:01       ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 3/8] Add configure check for std::thread Tom Tromey
2019-05-30 11:34   ` Pedro Alves [this message]
2019-05-29 21:29 ` [PATCH v3 7/8] Demangle minsyms in parallel Tom Tromey
2019-05-30 14:19   ` Pedro Alves
2019-05-30 22:22     ` Tom Tromey
2019-05-29 22:03 ` [PATCH v3 6/8] Introduce thread-safe way to handle SIGSEGV Tom Tromey
2019-05-30 13:40   ` Pedro Alves
2019-06-09 15:43     ` Tom Tromey

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=04acc58e-d293-1753-a106-15b94c5d5cbf@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).