From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 2/2] Patch to assembler to strip LOCK prefix.
Date: Wed, 7 Oct 2015 23:09:55 +0100 [thread overview]
Message-ID: <56159833.6080005@mind.be> (raw)
In-Reply-To: <1444211584.2759.10.camel@intel.com>
On 07-10-15 10:53, Kinsella, Ray wrote:
> Hi Arnout,
>
> On Sun, 2015-10-04 at 19:15 +0100, Arnout Vandecappelle wrote:
>> We now have a toolchain wrapper both for internal and external toolchains. This
>> will allow you to reliably pass options to the compiler. So we'd preferably use
>> that approach.
>
> Ok - I will investigate - any examples I can look at?
>
>> Also, we think it's worthwhile to add a new subarchitecture for the Quark in
>> arch/Config.in.x86. This should set the arch and tune options to i586, but the
>> toolchain wrapper can then carry an option that adds -Wa,-momit-lock-prefix=yes.
>> This also fixes the problem for external toolchains.
>
> Ok - I actually proto-typed this and I couldn't get it to work reliably,
> hence the nasty patch.
Should be fairly simple with the toolchain wrapper. I think it it best to
refactor toolchain/toolchain-wrapper.mk a little to create a new variable to
contain the BR_ADDITIONAL_CFLAGS, and then conditionally add the -Wa,-momit-...
option to it.
> I should have it on a branch (I hope), I can dust it off.
>
>> So the proposal is that you create a first patch that adds BR2_x86_quark and
>> adds -Wa,-momit-lock-prefix=yes, and then a second patch that adds the Galileo2
>> defconfig.
>
> ok
>
>> I have now marked both patches as Changes Requested in out patch tracking
>> system, so please resubmit a new version that fixes the above comments,
>> otherwise we'll forget about your contribution.
>
> ok - will followup.
> (is the patch tracking system public?)
http://patchwork.ozlabs.org/project/buildroot/list/
If you create a login with the same email address as the one you send patches
from, then you can update the state of your own patches (e.g. mark them as
Superseded when you send a new version).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-10-07 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 11:49 [Buildroot] [PATCH v5 2/2] Patch to assembler to strip LOCK prefix Kinsella, Ray
2015-10-04 18:15 ` Arnout Vandecappelle
2015-10-07 9:53 ` Kinsella, Ray
2015-10-07 10:09 ` Baruch Siach
2015-10-07 22:09 ` Arnout Vandecappelle [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=56159833.6080005@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox