From: David Woodhouse <dwmw2@infradead.org>
To: dl9pf@gmx.de
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
llvmlinux@lists.linuxfoundation.org, behanw@converseincode.com
Subject: Re: [PATCH] Make alignment cflags configurable.
Date: Wed, 12 Aug 2015 13:50:44 +0100 [thread overview]
Message-ID: <1439383844.3100.81.camel@infradead.org> (raw)
In-Reply-To: <1439382775-28009-1-git-send-email-dl9pf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Wed, 2015-08-12 at 14:32 +0200, dl9pf@gmx.de wrote:
> From: Jan-Simon Möller <dl9pf@gmx.de>
>
> This patch adds switches for
> -falign-jumps=1
> and
> -falign-loops=1
>
> Default is off by intention to allow seamless operation.
>
> Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
You could mention that this is to fix the clang build. But why is it
needed? It isn't that clang just doesn't accept the option, is it?
Otherwise we could just use $(call cc-option, -falign-jumps=1) etc.
Did you get to the bottom of the clang failure here? Just turning this
off without a coherent explanation doesn't seem like the right thing to
do.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-08-12 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 12:32 dl9pf
2015-08-12 12:50 ` David Woodhouse [this message]
2015-08-12 22:30 ` Jan-Simon Moeller
2015-08-12 22:37 ` H. Peter Anvin
2015-08-12 23:17 ` [llvmlinux] " Jan-Simon Moeller
2015-08-12 23:37 ` David Woodhouse
2015-08-12 23:59 ` Jan-Simon Moeller
2015-08-13 0:05 ` David Woodhouse
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=1439383844.3100.81.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=behanw@converseincode.com \
--cc=dl9pf@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®