linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Murilo Opsfelder Araújo" <mopsfelder@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] powerpc/boot: Build wrapper for an appropriate CPU
Date: Thu, 31 Mar 2022 18:09:58 -0500	[thread overview]
Message-ID: <20220331230958.GA614@gate.crashing.org> (raw)
In-Reply-To: <815770fb-3247-baab-f8ca-eed7b99213d1@gmail.com>

On Wed, Mar 30, 2022 at 11:05:19PM -0300, Murilo Opsfelder Araújo wrote:
> I think it was a fortunate coincidence that the default cpu type of your 
> gcc is
> compatible with your system.  If the distro gcc moves its default to a 
> newer cpu
> type than your system, this bug would happen again.

Indeed.  But why would you use a GCC from a distro that requires p10
when you target something older?

> The command "gcc -v |& grep with-cpu" will show you the default cpu type 
> for 32
> and 64-bit that gcc was configured.

Only if it was configured with --with-cpu*.  Most people do not.  If
someone builds compilers with non-default defaults like this, they had
better communicate that clearly to all their users, to avoid confusion
and disappointments.

There should be some easy way to show this default with GCC, but there
currently is none.  I'll see what I can do (just to make my own life
easier, we frequently get bug reports from people who use a different
-mcpu= than what they think they do :-) )


Segher

  parent reply	other threads:[~2022-03-31 23:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 11:24 [PATCH] powerpc/boot: Build wrapper for an appropriate CPU Joel Stanley
2022-03-30 11:33 ` Christophe Leroy
2022-03-30 11:39   ` Joel Stanley
2022-03-31 23:00     ` Segher Boessenkool
2022-03-31  2:05 ` Murilo Opsfelder Araújo
2022-03-31  5:01   ` Joel Stanley
2022-03-31 15:19     ` Murilo Opsfelder Araújo
2022-03-31 23:44       ` Segher Boessenkool
2022-04-06  7:08         ` Joel Stanley
2022-04-07 18:43           ` Murilo Opsfelder Araújo
2022-04-07 20:33             ` Segher Boessenkool
2022-03-31 23:09   ` Segher Boessenkool [this message]
2022-05-15 10:12 ` Michael Ellerman

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=20220331230958.GA614@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mopsfelder@gmail.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;
as well as URLs for NNTP newsgroup(s).