public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jeffrey Walton <noloader@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC 7 on ppc64le does not recognize vec_xl_be?
Date: Sat, 16 Nov 2019 22:33:00 -0000	[thread overview]
Message-ID: <CAH6eHdTscfhTAekPujxe3tMY2=n2gEV-Yww7T+G8WUx1E8bWrA@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8k2UPqxzWTsZkNTD59JxSA5AizEZJYYDpw_KTRJ0+zqVQ@mail.gmail.com>

On Sat, 16 Nov 2019 at 21:25, Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Sat, Nov 16, 2019 at 1:26 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> >  ...
> > I already sent the following to Jeffrey 8 hours ago (off-list, because
> > I could only send HTML mail at the time):
> >
> > "Those are the docs for GCC trunk. That function is not listed in the
> > docs for GCC 7."
>
> GCC tells me it supports the load by accepting -mcpu=power9 and
> defining _ARCH_PWR9.
>
> The problems with GCC seem to be a little larger then inaccurate docs.

What? You're talking nonsense.

You said:
"According to the GCC docs vec_xl_be is available with ISA 3.0:
https://gcc.gnu.org/onlinedocs/gcc/PowerPC-AltiVec-Built-in-Functions-Available-on-ISA-3_002e0.html
"

You are consulting the docs for GCC trunk and assuming they apply to
GCC 7. That's simply wrong.

The corresponding docs for GCC 7 are at:
https://gcc.gnu.org/onlinedocs/gcc-7.5.0/gcc/PowerPC-AltiVec_002fVSX-Built-in-Functions.html#PowerPC-AltiVec_002fVSX-Built-in-Functions

It doesn't mention vec_xl_be in the functions available with
-mcpu=power9. So why do you think GCC 7 might not recognise that
function? Hmm, maybe because it isn't supported by GCC 7.

The docs are accurate. The docs for GCC 7 say which functions
-mcpu=power9 enables FOR GCC 7, and that doesn't include the function
you're trying to use.

The docs for GCC trunk say which functions -mcpu-power9 enables FOR
GCC TRUNK. Not for all versions. The intro to the pages you're looking
at says "It corresponds to the compilers (GCC) version 10.0.0." so
you're simply wrong to assume it also corresponds to older versions.
It doesn't. For older versions, see the docs for those versions.

  parent reply	other threads:[~2019-11-16 22:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16  1:07 Jeffrey Walton
2019-11-16 11:25 ` Segher Boessenkool
2019-11-16 11:45   ` Jeffrey Walton
2019-11-16 14:26     ` Segher Boessenkool
2019-11-16 14:47       ` Jeffrey Walton
2019-11-16 17:41         ` Segher Boessenkool
2019-11-16 18:26           ` Jonathan Wakely
2019-11-16 21:25             ` Jeffrey Walton
2019-11-16 22:19               ` Segher Boessenkool
2019-11-16 22:26                 ` Jeffrey Walton
2019-11-16 22:34                   ` Jonathan Wakely
2019-11-18 18:29                   ` Richard Sandiford
2019-11-18 19:10                     ` Segher Boessenkool
2019-11-18 20:05                     ` Martin Sebor
2019-11-18 20:20                       ` Segher Boessenkool
2019-11-16 22:33               ` Jonathan Wakely [this message]
2019-11-16 22:40                 ` Jeffrey Walton
2019-11-16 22:43                   ` Jonathan Wakely
2019-11-16 22:52                   ` Segher Boessenkool
2019-11-16 22:56                     ` Jeffrey Walton
2019-11-16 22:58                       ` Jonathan Wakely
2019-11-16 15:24       ` Xi Ruoyao
2019-11-16 17:47         ` Segher Boessenkool

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='CAH6eHdTscfhTAekPujxe3tMY2=n2gEV-Yww7T+G8WUx1E8bWrA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=noloader@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 read-only IMAP folder(s) and NNTP newsgroup(s).