All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Please pull from 'for_paulus' branch
Date: Fri, 29 Jun 2007 11:51:02 +0200	[thread overview]
Message-ID: <86458f827c7ba4a92be4861c1cd3b928@kernel.crashing.org> (raw)
In-Reply-To: <18052.53604.173632.186062@cargo.ozlabs.ibm.com>

>> It is not.  -mcpu=powerpc64 doesn't select an ABI, and your
>> GCC presumably defaults to the 32-bit ABI.  Use -m64 on the
>> GCC command line, too, you need it, and it solves this issue
>> as a side effect.
>
> No, actually the command line had -m64 on it.  The situation is this:
>
> gcc -m64 -mtune=power4 works
> gcc -m64 -mcpu=powerpc64 -mtune=power4 fails.
>
> The problem is in the spec file where it works out what parameters to
> pass to `as'.  Without any -mcpu it correctly defaults to passing
> -mppc64 (when -m64 is given).  It then also has a list of -mcpu values
> and the corresponding flag to pass to as, but powerpc64 isn't in that
> list.  Thus with -mcpu=powerpc64 we don't get -mppc64 passed to as.

Oh okay, badness.  What's the GCC PR #?


Segher

  reply	other threads:[~2007-06-29  9:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  5:24 Please pull from 'for_paulus' branch Kumar Gala
2007-06-29  6:26 ` Paul Mackerras
2007-06-29  7:04   ` Kumar Gala
2007-06-29  9:15   ` Segher Boessenkool
2007-06-29  9:31     ` Paul Mackerras
2007-06-29  9:51       ` Segher Boessenkool [this message]
2007-06-29 13:45   ` Arnd Bergmann
2007-06-29 14:44     ` Kumar Gala
2007-06-29 16:05       ` Arnd Bergmann
2007-06-29 16:09         ` Kumar Gala
2007-06-29 16:10         ` Kumar Gala
2007-06-29 15:22   ` Andreas Schwab
2007-06-30  6:57     ` Paul Mackerras
2007-06-30  8:10       ` Andreas Schwab
2007-06-30  8:14         ` Paul Mackerras
2007-06-30  8:49           ` Andreas Schwab
2007-06-30 10:57       ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 21:01 Kumar Gala
2007-07-24  2:56 ` Kumar Gala
2007-07-25  6:43 ` Zang Roy-r61911
2007-07-10  5:42 Kumar Gala
2007-05-15 22:20 Kumar Gala
2007-05-17 10:49 ` Paul Mackerras
2007-05-17 12:05   ` Segher Boessenkool
2007-05-17 12:58     ` Kumar Gala
2007-05-17 13:00   ` Kumar Gala
2007-05-18  6:15     ` Paul Mackerras
2007-05-18 16:51       ` Kumar Gala
2007-02-17 22:38 Kumar Gala
2007-02-17 22:44 ` Kumar Gala
2007-02-13 22:16 Kumar Gala
2007-02-08 21:50 Kumar Gala
2007-02-08 21:52 ` Please pull from 'for_paulus' branch Kumar Gala
2007-02-07  7:51 Kumar Gala
2006-12-08  8:51 Kumar Gala

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=86458f827c7ba4a92be4861c1cd3b928@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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.