All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
	Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Matt Turner <mattst88@gmail.com>
Subject: Re: [PATCH] alpha: makefile: don't enforce small data model for kernel builds
Date: Mon, 18 Mar 2013 17:11:15 +1300	[thread overview]
Message-ID: <BFB01C0A-95E5-4C2B-8AF2-A06BE1FF74E0@orcon.net.nz> (raw)
In-Reply-To: <1363556926-21097-1-git-send-email-will.deacon@arm.com>

On 18/03/2013, at 10:48 AM, Will Deacon wrote:
> Due to all of the goodness being packed into today's kernels, the
> resulting image isn't as slim as it once was.
>
> In light of this, don't pass -msmall-data to the tools, which  
> results in
> link failures due to impossible relocations when compiling anything  
> but
> the most trivial configurations.

I think many of us have been using -mlarge-data when compiling with  
gcc-4.6 or later so maybe it is time to get the change upstream.

The interesting thing is that the kernel still compiles fine with  
gcc-4.5 and the relocation errors only appear if compiling with  
gcc-4.6 or later.  I had asked before on this forum what had changed  
with gcc-4.6 that results in the extra usage of the small data area  
but never got an answer.  I am still curious to know.

BTW, the phrase "to the tools" in the commit message makes me think  
immediately of the tools directory (containing perf, etc.) which is  
not what is intended.

Matt:  Are you able to collect up this and the other patches of Will  
and get them sent to Linus?

Cheers
Michael.


  reply	other threads:[~2013-03-18  4:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 21:48 [PATCH] alpha: makefile: don't enforce small data model for kernel builds Will Deacon
2013-03-18  4:11 ` Michael Cree [this message]
2013-03-25 13:37   ` Will Deacon
2013-03-25 13:37     ` Will Deacon
2013-03-25 15:09     ` Tobias Klausmann
2013-03-25 20:06       ` Michael Cree
2013-03-25 20:55         ` Matt Turner
2013-03-26  1:52           ` Rob Landley
2013-03-27 17:56         ` Tobias Klausmann
2013-03-28 10:25           ` Tobias Klausmann
2013-04-03 18:02   ` Will Deacon
2013-03-18 18:18 ` Thorsten Kranzkowski

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=BFB01C0A-95E5-4C2B-8AF2-A06BE1FF74E0@orcon.net.nz \
    --to=mcree@orcon.net.nz \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=rth@twiddle.net \
    --cc=will.deacon@arm.com \
    /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.