public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: ARC build -O3 (was Re: subtle side effect of commit a1c48bb160f836)
Date: Thu, 02 Jul 2015 21:50:37 +0200	[thread overview]
Message-ID: <5595960D.8040208@suse.cz> (raw)
In-Reply-To: <5594CBBE.2030302@synopsys.com>

Dne 2.7.2015 v 07:27 Vineet Gupta napsal(a):
> On Wednesday 01 July 2015 08:49 PM, Michal Marek wrote:
>> On Wed, Jun 24, 2015 at 05:50:16PM +0530, Vineet Gupta wrote:
>>> On Thursday 18 June 2015 04:02 PM, Vineet Gupta wrote:
>>>> On Thursday 18 June 2015 03:44 PM, Michal Marek wrote:
>>>>> Uh, this is not what I meant. KCFLAGS is a *user* setting. It's meant to
>>>>> be set in the environment or command line.
>>>>
>>>> Well I don't want to rely on external settings whatsoever to enforce this. If this
>>>> is not the right way, what do u suggest I do to help fix this.
>>>
>>>
>>> Can I keep this seeming abuse of KCFLAGS or do u suggest alternate approach I can
>>> code up !
>>
>> Hi Vineet, sorry for the late reply.
> 
> NP !
> 
>> I had something like the below
>> patch in mind, simply allow arc to specify -O3 in ARCH_CFLAGS (that part
>> I'm leaving up to you).
> 
> See below !
> 
>> From e458fdf4ae37e1adce81b58d96b1075b4f0656e6 Mon Sep 17 00:00:00 2001
>> From: Michal Marek <mmarek@suse.com>
>> Date: Wed, 1 Jul 2015 17:13:16 +0200
>> Subject: [PATCH] kbuild: Allow arch Makefiles to override {cpp,ld,c}flags
>>
>> Since commit a1c48bb1 (Makefile: Fix unrecognized cross-compiler command
>> line options), the arch Makefile is included earlier by the main
>> Makefile, preventing the arc architecture to set its -O3 compiler
>> option. Since there might be more use cases for an arch Makefile to
>> fine-tune the options, add support for ARCH_CPPFLAGS, ARCH_AFLAGS and
>> ARCH_CFLAGS variables that are appended to the respective kbuild
>> variables. The user still has the final say via the KCPPFLAGS, KAFLAGS
>> and KCFLAGS variables.
>>
>> Reported-by: Vineet Gupta <Vineet.Gupta1@synopsys.com>
>> Signed-off-by: Michal Marek <mmarek@suse.com>
> 
> Sweet, that works for me with the following patch below.
> 
> Some logistics things:
> - It would be nice to keep both of these patches together - do u want to do
>   that or want me to pick this one up

Feel free to pick up my patch.


> - For ARC this fixes a regression starting 3.16 - so I'll need a stable backport
>   which but obviously requires above to go to stable. Do u have any issues with
>   that. Shall we do the stable request after these hit the mainline...

Or just add

  Cc: stable@vger.kernel.org # 3.16+

to the patches.

Michal

  reply	other threads:[~2015-07-02 19:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18  6:47 subtle side effect of commit a1c48bb160f836 Vineet Gupta
2015-06-18  7:10 ` Geert Uytterhoeven
2015-06-18  7:33   ` Vineet Gupta
2015-06-18  7:37     ` Geert Uytterhoeven
2015-06-18  8:00       ` Vineet Gupta
2015-06-18  8:13   ` Michal Marek
2015-06-18  8:45     ` Vineet Gupta
2015-06-18  8:55       ` Geert Uytterhoeven
2015-06-18  9:16         ` Vineet Gupta
2015-06-18 10:14       ` Michal Marek
2015-06-18 10:32         ` Vineet Gupta
2015-06-24 12:20           ` Vineet Gupta
2015-07-01 15:19             ` Michal Marek
2015-07-02  5:27               ` ARC build -O3 (was Re: subtle side effect of commit a1c48bb160f836) Vineet Gupta
2015-07-02 19:50                 ` Michal Marek [this message]
2015-07-03  2:58                   ` Vineet Gupta

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=5595960D.8040208@suse.cz \
    --to=mmarek@suse.cz \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.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