Linux-Next discussions
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tony@bakeyournoodle.com
Cc: sfr@canb.auug.org.au, paul.gortmaker@windriver.com,
	sparclinux@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: New build failures in sparc.
Date: Tue, 13 Mar 2012 21:46:09 -0700 (PDT)	[thread overview]
Message-ID: <20120313.214609.1139946570476396180.davem@davemloft.net> (raw)
In-Reply-To: <20120314040102.GA26084@thor.bakeyournoodle.com>

From: Tony Breeds <tony@bakeyournoodle.com>
Date: Wed, 14 Mar 2012 15:01:02 +1100

> On Tue, Mar 13, 2012 at 05:37:41PM -0700, David Miller wrote:
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Wed, 14 Mar 2012 10:28:30 +1100
>> 
>> > Yeah, we updated our sparc64 toolchain yesterday ... Tony says he
>> > will try applying the patch(es) from the bugzilla.
>> 
>> Meanwhile I'll add a workaround to the sparc makefiles, and
>> push that to Linus.  This way it will work no matter what
>> combination of tools someone has.
> 
> Thanks Dave, we may be hitting a related but different issue as gcc
> 4.6.3 seems to have that patch already.

See the patch I sent to Linus which landed in his tree an hour or so
ago:

--------------------
[PATCH] sparc32: Add -Av8 to assembler command line.

Newer version of binutils are more strict about specifying the
correct options to enable certain classes of instructions.

The sparc32 build is done for v7 in order to support sun4c systems
which lack hardware integer multiply and divide instructions.

So we have to pass -Av8 when building the assembler routines that
use these instructions and get patched into the kernel when we find
out that we have a v8 capable cpu.

Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
---
 arch/sparc/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/sparc/Makefile b/arch/sparc/Makefile
index ad1fb5d..eddcfb3 100644
--- a/arch/sparc/Makefile
+++ b/arch/sparc/Makefile
@@ -31,7 +31,7 @@ UTS_MACHINE    := sparc
 
 #KBUILD_CFLAGS += -g -pipe -fcall-used-g5 -fcall-used-g7
 KBUILD_CFLAGS += -m32 -pipe -mno-fpu -fcall-used-g5 -fcall-used-g7
-KBUILD_AFLAGS += -m32
+KBUILD_AFLAGS += -m32 -Wa,-Av8
 
 #LDFLAGS_vmlinux = -N -Ttext 0xf0004000
 #  Since 2.5.40, the first stage is left not btfix-ed.
-- 
1.7.6.5

  reply	other threads:[~2012-03-14  4:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 22:28 New build failures in sparc Paul Gortmaker
2012-03-13 22:48 ` David Miller
2012-03-13 23:28   ` Stephen Rothwell
2012-03-14  0:37     ` David Miller
2012-03-14  0:58       ` Stephen Rothwell
2012-03-14  4:01       ` Tony Breeds
2012-03-14  4:46         ` David Miller [this message]
2012-03-14  5:02           ` Stephen Rothwell
2012-03-13 23:31   ` Paul Gortmaker

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=20120313.214609.1139946570476396180.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.org \
    --cc=tony@bakeyournoodle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox