From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
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:34:00 -0000 [thread overview]
Message-ID: <CAH6eHdTBt7sGZ5X_jW6iZtjX_aRBDtv3AvRdhzSDqTp21n_icQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8ktYwXoKGxrWCCYLhe+bhwdOd33pisP1auM20u-=rYemg@mail.gmail.com>
On Sat, 16 Nov 2019 at 22:26, Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Sat, Nov 16, 2019 at 5:19 PM Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> >
> > On Sat, Nov 16, 2019 at 04:25:18PM -0500, Jeffrey Walton wrote:
> > > On Sat, Nov 16, 2019 at 1:26 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> > > > ...
> > > The problems with GCC seem to be a little larger then inaccurate docs.
> >
> > The GCC docs are perfectly accurate for this as well.
> >
> > GCC 7 is older than this revision of the ELFv2 specification, and we never
> > backported this feature: only very important features are backported. It
> > could have made 7.2, over two years ago, but it wasn't considered important
> > enough to backport.
>
> Then you don't understand how search works in 2019 and how users
> search for information. We cannot search for the absence of
> information.
The information is there:
https://gcc.gnu.org/onlinedocs/gcc-7.5.0/gcc/PowerPC-AltiVec_002fVSX-Built-in-Functions.html#PowerPC-AltiVec_002fVSX-Built-in-Functions
That lists the functions enabled by -mcpu=power9 in GCC 7. Stop
reading the wrong docs.
next prev parent reply other threads:[~2019-11-16 22:34 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 [this message]
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
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=CAH6eHdTBt7sGZ5X_jW6iZtjX_aRBDtv3AvRdhzSDqTp21n_icQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=noloader@gmail.com \
--cc=segher@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 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).