From: Matthew Weber <matthew.weber@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xerces: enable threads if available
Date: Sat, 6 Oct 2018 15:59:24 -0500 [thread overview]
Message-ID: <CANQCQpYzCdj7JobpWto-RMJ_-pzvhv29YUnH-HwWr1bLj2yBzg@mail.gmail.com> (raw)
In-Reply-To: <20181006201308.20461-1-fontaine.fabrice@gmail.com>
Fabrice,
On Sat, Oct 6, 2018 at 3:13 PM Fabrice Fontaine
<fontaine.fabrice@gmail.com> wrote:
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
> package/xerces/xerces.mk | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/package/xerces/xerces.mk b/package/xerces/xerces.mk
> index a25641fb45..da088d8e1c 100644
> --- a/package/xerces/xerces.mk
> +++ b/package/xerces/xerces.mk
> @@ -10,9 +10,7 @@ XERCES_SITE = http://archive.apache.org/dist/xerces/c/3/sources
> XERCES_LICENSE = Apache-2.0
> XERCES_LICENSE_FILES = LICENSE
> XERCES_INSTALL_STAGING = YES
> -XERCES_CONF_OPTS = \
> - --disable-threads \
I went back and checked the history on why threading was disabled by
default. It looks like there wasn't a specific reason. Just a
package bump and change of configuration style.
https://git.busybox.net/buildroot/commit/package/xerces/xerces.mk?id=324f61f7982c64ebd4a457467b33a6984bd8a584
> +ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
> +XERCES_CONF_OPTS += --enable-threads
> +else
> +XERCES_CONF_OPTS += --disable-threads
> +endif
> +
Does this yield a pretty good performance increase? Wonder how they
bound the thread number to use on target when it runs.
Matt
next prev parent reply other threads:[~2018-10-06 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 20:13 [Buildroot] [PATCH 1/1] xerces: enable threads if available Fabrice Fontaine
2018-10-06 20:59 ` Matthew Weber [this message]
2018-10-06 21:51 ` Fabrice Fontaine
2018-10-09 13:06 ` Thomas Petazzoni
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=CANQCQpYzCdj7JobpWto-RMJ_-pzvhv29YUnH-HwWr1bLj2yBzg@mail.gmail.com \
--to=matthew.weber@rockwellcollins.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.