From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gcc atomic instruction support for armv5te
Date: Mon, 22 Mar 2010 10:53:58 -0700 [thread overview]
Message-ID: <20100322175358.GA10417@gmail.com> (raw)
In-Reply-To: <4BA720E0.10806@dresearch.de>
On (22/03/10 08:48), Steffen Sledz wrote:
> Khem Raj wrote:
> >> As mentioned before i try to create a recipe for rsyslog.
> >>
> >> Now i hit the next big problem. The last item at
> >> http://www.rsyslog.com/doc-build_from_repo.html says that
> >>
> >> "The availability of atomic instructions is vital for rsyslog"
> >>
> >> The gcc version 4.3.3 which is used for armv5te by default
> >> misses this. :(
> >>
> >> Is there a newer gcc version with atomic instruction for armv5te
> >> machines available/tested? I heard rumors that 4.4.3 shell
> >> have it?
> >
> > yes 4.4+ should have them as intrinsic functions.
>
> Unfortunately angstrom uses 4.3.3 by default.
>
> Is it possible to build just this one package with a newer gcc?
though its possible I wouldnt go for having a different gcc for one package
is there an older version of rsyslog which does not use the intrinsics ?
you might also look at backporting intrinsics to gcc 4.3 which might be a
bit hairy
>
> > Which ones are needed by rsyslog ?
>
> __sync_fetch_and_sub
> __sync_fetch_and_add
> __sync_fetch_and_or
> __sync_fetch_and_and
> __sync_sub_and_fetch
> __sync_lock_test_and_set
> __sync_bool_compare_and_swap
> __sync_val_compare_and_swap
>
> Steffen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-03-22 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 11:37 gcc atomic instruction support for armv5te Steffen Sledz
2010-03-21 8:12 ` Khem Raj
2010-03-22 7:48 ` Steffen Sledz
2010-03-22 17:53 ` Khem Raj [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=20100322175358.GA10417@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.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 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.