From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: xtensa: fix atomic NAND code generation
Date: Fri, 28 Sep 2018 14:47:07 +0200 [thread overview]
Message-ID: <87sh1t7pro.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180905164839.14360-1-jcmvbkbc@gmail.com> (Max Filippov's message of "Wed, 5 Sep 2018 09:48:39 -0700")
>>>>> "Max" == Max Filippov <jcmvbkbc@gmail.com> writes:
> xtensa gcc incorrectly generates code for atomic NAND operation as
> ~a1 & a2 instead of ~(a1 & a2). Fix that.
> Backported from: r264087
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Committed to 2018.02.x and 2018.05.x after dropping the gcc 8.x patch,
thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-09-28 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 16:48 [Buildroot] [PATCH] package/gcc: xtensa: fix atomic NAND code generation Max Filippov
2018-09-05 19:15 ` Thomas Petazzoni
2018-09-28 12:47 ` Peter Korsgaard [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=87sh1t7pro.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.