This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 06/22] Makefile.in: hack in -lpthread
- From: Jeff Law <law at redhat dot com>
- To: David Malcolm <dmalcolm at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 1 Sep 2017 12:13:18 -0600
- Subject: Re: [PATCH 06/22] Makefile.in: hack in -lpthread
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=law at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D114C7EA9B
- References: <1501884293-9047-1-git-send-email-dmalcolm@redhat.com> <1501884293-9047-7-git-send-email-dmalcolm@redhat.com>
On 08/04/2017 04:04 PM, David Malcolm wrote:
> The checker.cc patch later in the kit can optionally make use of pthread
> if available.
>
> Doing it properly would involve some configure checks; this patch simply
> hacks in -lpthread into LIB unconditionally for now.
>
> gcc/ChangeLog:
> * Makefile.in (LIB): Hack in -lpthread.
Obviously this would need to be improved before it could move forward.
What's the advantage of firing off a thread vs the usual fork/exec
model? fork/exec is something we know how to deal with across all the
hosts GCC supports.
jeff