From: Christopher Li <sparse@chrisli.org>
To: Kim Phillips <kim.phillips@linaro.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
lng-odp@linaro.org, bill.fischofer@linaro.org,
petri.savolainen@linaro.org, mike.holmes@linaro.org
Subject: Re: [PATCH] sparse: add built-in atomic memory access identifiers
Date: Sat, 21 Dec 2013 09:22:55 -0800 [thread overview]
Message-ID: <CANeU7QkkFaPrqZi0OW1-Myxm1ObdAHA4xLfCR2bS90PM_Y5VKw@mail.gmail.com> (raw)
In-Reply-To: <20131211150013.e009efdb3fa2321f113a8a8d@linaro.org>
On Wed, Dec 11, 2013 at 1:00 PM, Kim Phillips <kim.phillips@linaro.org> wrote:
> this patch stops sparse from complaining about them not being
> defined:
>
> source/odp_spinlock.c:41:10: error: undefined identifier '__sync_lock_release'
> source/odp_spinlock.c:54:10: error: undefined identifier '__sync_lock_release'
> ./odp_atomic.h:112:16: error: undefined identifier '__sync_fetch_and_add'
>
> Reported-by: Mike Holmes <mike.holmes@linaro.org>
> Signed-off-by: Kim Phillips <kim.phillips@linaro.org>
Applied and pushed.
Chris
prev parent reply other threads:[~2013-12-21 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e016529d-1344-4eaa-8419-86cdf1e830cb@linaro.org>
[not found] ` <20131210125236.b44159c60acfd62b30b9bc69@linaro.org>
[not found] ` <CAKb83kaz+csV4Q=0P5Q+L75_CxYnL=RrDh4mSTujPmzJ9B7K-g@mail.gmail.com>
[not found] ` <e444e44d-ffb4-4ba0-86fd-9b66bc1b08d5@linaro.org>
[not found] ` <CADz3at2h9gDJkEz9FctvvPqj7_isoXj_hpPzJiQzSi2UNyn97g@mail.gmail.com>
[not found] ` <CAKb83kYKo=YP4JC2cjo-Y76xEvC45CM=5Wf9rO1Hv-06OSt5-Q@mail.gmail.com>
[not found] ` <CADz3at1A3id81XpKFf3gJhutWEpFi4zM0+xF=cfY-h_+ABd=gw@mail.gmail.com>
[not found] ` <20131211120204.4e17a616138823d09c89d298@linaro.org>
[not found] ` <CAKb83kZ4jYeiFAxpxqVwLtWYA3sobrN0vGDRzK0vs_jommsCwQ@mail.gmail.com>
[not found] ` <CADz3at0E7W=V17mO6D6hZrLp82VoC42_Jz==iSVUykz6+76phQ@mail.gmail.com>
[not found] ` <e92f5ecc-097b-401b-8554-6d3ada6be667@linaro.org>
2013-12-11 21:00 ` [PATCH] sparse: add built-in atomic memory access identifiers Kim Phillips
2013-12-21 17:22 ` Christopher Li [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=CANeU7QkkFaPrqZi0OW1-Myxm1ObdAHA4xLfCR2bS90PM_Y5VKw@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=bill.fischofer@linaro.org \
--cc=kim.phillips@linaro.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lng-odp@linaro.org \
--cc=mike.holmes@linaro.org \
--cc=petri.savolainen@linaro.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;
as well as URLs for NNTP newsgroup(s).