public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85830] vec_popcntd is improperly defined in altivec.h
Date: Fri, 04 Sep 2020 18:23:37 +0000 [thread overview]
Message-ID: <bug-85830-4-9oAIApJdKT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85830-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Carl Love <carll@gcc.gnu.org>:
https://gcc.gnu.org/g:e86814328251ea7da83038605df01d8def8d873a
commit r10-8710-ge86814328251ea7da83038605df01d8def8d873a
Author: Carl Love <cel@us.ibm.com>
Date: Thu Aug 27 13:36:13 2020 -0500
rs6000, remove improperly defined and unsupported builtins.
gcc/ChangeLog
2020-08-31 Carl Love <cel@us.ibm.com>
PR target/85830
* config/rs6000/altivec.h (vec_popcntb, vec_popcnth, vec_popcntw,
vec_popcntd): Remove defines.
next prev parent reply other threads:[~2020-09-04 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85830-4@http.gcc.gnu.org/bugzilla/>
2020-08-27 18:08 ` cel at us dot ibm.com
2020-08-27 18:15 ` cel at us dot ibm.com
2020-08-27 19:30 ` munroesj at gcc dot gnu.org
2020-08-27 19:38 ` cel at us dot ibm.com
2020-08-28 15:46 ` bergner at gcc dot gnu.org
2020-08-31 23:24 ` cvs-commit at gcc dot gnu.org
2020-09-04 18:23 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-04 18:28 ` carll at gcc dot gnu.org
2020-09-04 18:29 ` carll at gcc dot gnu.org
2020-09-07 12:59 ` segher at gcc dot gnu.org
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=bug-85830-4-9oAIApJdKT@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).