From: Ed Blake <ed.blake@sondrel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain-external: add option for OpenMP support
Date: Mon, 25 Mar 2019 11:27:41 +0000 [thread overview]
Message-ID: <20190325112550.56b40d7d@blake-linux> (raw)
In-Reply-To: <20190322211534.GH2660@scaer>
Hi Yann,
On Fri, 22 Mar 2019 22:15:34 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Ed, All,
>
> On 2019-03-22 16:59 +0000, Ed Blake spake thusly:
> > Add new BR2_TOOLCHAIN_HAS_OPENMP option for toolchains with OpenMP
> > support.
>
> With your series, there is no user of libgomp in Buildroot, so I
> suppose this is for your own local packages, right?
Yes, it's for a local package.
> Actually, if we have packages in Buildroot that may use OpenMP, then it
> is only optional for them, then. Do you know of such a package? The goal
> being to actually add a runtime-test that gomp works.
The following packages *could* use OpenMP, but currently disable it:
imagemagick
beecrypt
libraw
gettext
And the following package uses OpenMP if BR2_GCC_ENABLE_OPENMP is enabled:
fftw
I wonder if BR2_GCC_ENABLE_OPENMP should select BR2_TOOLCHAIN_HAS_OPENMP, in
the same way that BR2_TOOLCHAIN_BUILDROOT_FORTRAN selects BR2_TOOLCHAIN_HAS_FORTRAN.
Then BR2_TOOLCHAIN_HAS_OPENMP would be checked in the fftw makefile instead of
BR2_GCC_ENABLE_OPENMP.
Regards,
Ed.
> > Signed-off-by: Ed Blake <ed.blake@sondrel.com>
>
> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> Regards,
> Yann E. MORIN.
>
> > ---
> > toolchain/Config.in | 3 +++
> > toolchain/toolchain-external/pkg-toolchain-external.mk | 4 ++++
> > 2 files changed, 7 insertions(+)
> >
> > diff --git a/toolchain/Config.in b/toolchain/Config.in
> > index bcbc3cf984..bf42e92e00 100644
> > --- a/toolchain/Config.in
> > +++ b/toolchain/Config.in
> > @@ -168,6 +168,9 @@ config BR2_TOOLCHAIN_HAS_SSP
> > config BR2_TOOLCHAIN_HAS_UCONTEXT
> > bool
> >
> > +config BR2_TOOLCHAIN_HAS_OPENMP
> > + bool
> > +
> > config BR2_TOOLCHAIN_SUPPORTS_PIE
> > bool
> >
> > diff --git a/toolchain/toolchain-external/pkg-toolchain-external.mk b/toolchain/toolchain-external/pkg-toolchain-external.mk
> > index db3570d96f..747837fdc6 100644
> > --- a/toolchain/toolchain-external/pkg-toolchain-external.mk
> > +++ b/toolchain/toolchain-external/pkg-toolchain-external.mk
> > @@ -144,6 +144,10 @@ TOOLCHAIN_EXTERNAL_LIBS += libquadmath.so*
> > endif
> > endif
> >
> > +ifeq ($(BR2_TOOLCHAIN_HAS_OPENMP),y)
> > +TOOLCHAIN_EXTERNAL_LIBS += libgomp.so.*
> > +endif
> > +
> > TOOLCHAIN_EXTERNAL_LIBS += $(call qstrip,$(BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS))
> >
> >
> > --
> > 2.17.1
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2019-03-25 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 16:59 [Buildroot] [PATCH 0/2] toolchain-external: add OpenMP support Ed Blake
2019-03-22 16:59 ` [Buildroot] [PATCH 1/2] toolchain-external: add option for " Ed Blake
2019-03-22 21:15 ` Yann E. MORIN
2019-03-25 11:27 ` Ed Blake [this message]
2019-03-25 16:57 ` Yann E. MORIN
2019-03-26 11:03 ` Ed Blake
2019-03-22 16:59 ` [Buildroot] [PATCH 2/2] toolchain-external: enable OpenMP for supporting toolchains Ed Blake
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=20190325112550.56b40d7d@blake-linux \
--to=ed.blake@sondrel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox