public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alan Modra <amodra@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] PR96493, powerpc local call linkage failure
Date: Fri, 7 Aug 2020 09:48:55 -0500	[thread overview]
Message-ID: <20200807144855.GA6753@gate.crashing.org> (raw)
In-Reply-To: <20200807032808.GI15695@bubble.grove.modra.org>

On Fri, Aug 07, 2020 at 12:58:08PM +0930, Alan Modra wrote:
> On Thu, Aug 06, 2020 at 05:34:03PM -0500, Segher Boessenkool wrote:
> > > +/* { dg-do run } */
> > > +/* { dg-options "-mdejagnu-cpu=powerpc64 -O2" } */
> > 
> > That is not a -mcpu= value you should ever use.  Please just pick a real
> > existing CPU, maybe p7 or p8 since this requires ELFv2 anyway?  Or, what
> > does it need here?  It isn't clear to me.  But you don't want a pseudo-
> > POWER3 with ELFv2 :-)
> 
> What I was trying to say by using cpu=powerpc64 is that this test has
> minimal requirements on the required cpu level to run the test.
> That's all.

That would be -mcpu=powerpc64le, which is the exact same as -mcpu=power8.
-mcpu=powerpc64 is something close to 620/630 (power3, but it is not
exactly the same as -mcpu=power3) :-)

> Changed to power8 and committed.

Thanks!


Segher

  reply	other threads:[~2020-08-07 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 13:28 Alan Modra
2020-08-06 22:34 ` Segher Boessenkool
2020-08-07  3:28   ` Alan Modra
2020-08-07 14:48     ` Segher Boessenkool [this message]
2020-08-11  9:08     ` Alan Modra
2020-08-11 16:35       ` Segher Boessenkool
2020-08-11 17:36         ` Peter Bergner
2020-08-11 18:30           ` Segher Boessenkool
2020-08-12  4:02             ` Alan Modra

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=20200807144855.GA6753@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=amodra@gmail.com \
    --cc=gcc-patches@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).