From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: openmp in gcc-cross
Date: Wed, 06 Aug 2008 12:41:02 +0200 [thread overview]
Message-ID: <g7bv3u$9d0$1@ger.gmane.org> (raw)
In-Reply-To: <1218008960.25732.178.camel@lenovo.internal.reciva.com>
Phil Blundell wrote:
> The error with gettext is just a straightforward "-lgomp not found" kind
> of thing. Gettext will compile OK with older, non-OpenMP-capable
> compilers: it checks for the -fopenmp flag during configure, but it
> expects (not unreasonably) that if you have an OpenMP capable compiler
> then you will also have the right libraries available.
>
> For people who don't want OpenMP I think the right thing is to have a
> global "USE_OPENMP" variable to turn off OpenMP support at the package
> level. For most autotools-using packages this is going to mean adding
> "--disable-openmp" to EXTRA_OECONF.
>
> You're right that OpenMP might indeed be overkill on some/most embedded
> systems, but embedded multi-threading is by no means unheard of and I
> guess it will become more popular as CPUs like the Cortex-A9 and newer
> Pentiums start to show up in these systems.
Speaking of cortex-A9 MPCore (and arm11 MPCore as well), how well does
linux (kernel + c library) support MP on arm? I heard horror stories
about missing memory barriers, but that was over a year ago.
> I verified that libgomp does compile OK with gcc 4.2.2, so I guess I'll
> go ahead and re-enable it for that version at least.
gcc 4.2.4 (re)built fine for me after your latest changes.
regards,
Koen
prev parent reply other threads:[~2008-08-06 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 8:19 openmp in gcc-cross Phil Blundell
2008-08-05 10:35 ` Koen Kooi
2008-08-05 12:13 ` Phil Blundell
2008-08-05 12:26 ` Koen Kooi
2008-08-06 0:57 ` Khem Raj
2008-08-06 7:49 ` Phil Blundell
2008-08-06 10:41 ` Koen Kooi [this message]
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='g7bv3u$9d0$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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