All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kumar.gala@freescale.com, tnt@246tNt.com,
	linuxppc-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
	olh@suse.de, akpm@osdl.org
Subject: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c
Date: Fri, 30 Jul 2004 22:48:28 +0200	[thread overview]
Message-ID: <20040730224828.0f06e37a.pochini@shiny.it> (raw)
In-Reply-To: <20040730190731.GQ16468@smtp.west.cox.net>

On Fri, 30 Jul 2004 12:07:31 -0700
Tom Rini <trini@kernel.crashing.org> wrote:

> 
> On Fri, Jul 30, 2004 at 08:59:01PM +0200, Giuliano Pochini wrote:
> 
> > On Thu, 29 Jul 2004 07:43:47 -0700
> > Tom Rini <trini@kernel.crashing.org> wrote:
> > > > I had no time to do a lot of testing, but it seems that binutils 2.15 +
> > > > gcc 3.3.3 is a bad one too. I didn't try to compile the kernel (which
> > > > may also break), but at least I couldn't compile gcc 3.4.1 with the
> > > > above combination. It seems that as doesn't get the -mxxx parameter
> > > > required to compile altivec stuff. Hacking the Makefile to make it
> > > > pass -Wa,-m7455 helped a little, but it eventually failed in another
> > > > weird way. I hadn't time to investigate further, sorry.
> > >
> > > Stock gcc-3.3.3 or from the hammer branch ?
> >
> > Stock.
>
> That is interesting.

Actually, I don't know what the "hammer" thing is. I downloaded gcc from one
of the gcc.gnu.org mirrors: IIRC ftp://ftp.irisa.fr/pub/mirrors/gcc.gnu.org/gcc/releases/gcc-3.4.1


> Olaf, is gcc-3.3.x + binutils-2.15 one of the
> combinations you've got in your matrix of toolchains?


gcc 3.3.3 + binutils 2.15 fails quite soon here:

  AS      arch/ppc/kernel/l2cr.o
arch/ppc/kernel/l2cr.S: Assembler messages:
arch/ppc/kernel/l2cr.S:110: Error: Unrecognized opcode: `dssall'
arch/ppc/kernel/l2cr.S:278: Error: Unrecognized opcode: `dssall'
arch/ppc/kernel/l2cr.S:387: Error: Unrecognized opcode: `dssall'
make[1]: *** [arch/ppc/kernel/l2cr.o] Error 1



--
Giuliano.

  reply	other threads:[~2004-07-30 20:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 15:46 [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 check Tom Rini
2004-07-28 22:00 ` Andrew Morton
2004-07-28 22:07   ` Tom Rini
2004-07-28 22:51     ` Andrew Morton
2004-07-29 15:04       ` Sylvain Munaut
2004-07-29  8:05     ` [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c Giuliano Pochini
2004-07-29 14:43       ` Tom Rini
2004-07-30 18:59         ` Giuliano Pochini
2004-07-30 19:07           ` Tom Rini
2004-07-30 20:48             ` Giuliano Pochini [this message]
2004-07-30 21:03               ` Tom Rini
2004-07-31 12:53                 ` Giuliano Pochini
2004-08-02 15:43                   ` Tom Rini
2004-08-04 10:22                 ` Wolfram Quester
2004-08-04 10:41                 ` Guido Guenther
2004-08-04 12:37                   ` Guido Guenther
2004-08-05 14:12                 ` Olaf Hering
2004-08-05 16:54                   ` Tom Rini
2004-08-05 17:00                     ` Olaf Hering
2004-08-05 17:20                       ` Tom Rini
2004-08-05 17:39                         ` Olaf Hering
2004-08-05 18:03                           ` Tom Rini
2004-08-05 18:00                     ` Olaf Hering
2004-08-05 18:14                       ` Tom Rini
2004-08-05 19:04                         ` Sam Ravnborg
2004-08-05 21:03                         ` Matt Porter
2004-08-06 15:32                         ` Olaf Hering
     [not found]                         ` <hhacx8hirb.fsf@alsvidh.mathematik.uni-muenchen.de>
2004-08-06 15:38                           ` [PATCH] ppc32: Fix building of certain CPU types (Was: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14) Tom Rini
2004-08-02  7:45             ` [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c Olaf Hering

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=20040730224828.0f06e37a.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=akpm@osdl.org \
    --cc=kumar.gala@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    --cc=tnt@246tNt.com \
    --cc=trini@kernel.crashing.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 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.