From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gcc atomic instruction support for armv5te
Date: Sun, 21 Mar 2010 01:12:36 -0700 [thread overview]
Message-ID: <20100321081236.GA6455@gmail.com> (raw)
In-Reply-To: <4B9E1C0D.5050806@dresearch.de>
On (15/03/10 12:37), Steffen Sledz 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. Which ones are needed by rsyslog ?
>
> Steffen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-03-21 8:15 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 [this message]
2010-03-22 7:48 ` Steffen Sledz
2010-03-22 17:53 ` Khem Raj
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=20100321081236.GA6455@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox