public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96933] rs6000: inefficient code for char/short vec CTOR
Date: Fri, 04 Sep 2020 09:33:35 +0000 [thread overview]
Message-ID: <bug-96933-4-9Ha0To7K1E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96933-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96933
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
CC| |bergner at gcc dot gnu.org,
| |linkw at gcc dot gnu.org,
| |segher at gcc dot gnu.org,
| |wschmidt at gcc dot gnu.org
Summary|inefficient code for |rs6000: inefficient code
|char/short vec CTOR |for char/short vec CTOR
Last reconfirmed| |2020-09-04
Target| |powerpc
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
next prev parent reply other threads:[~2020-09-04 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 9:31 [Bug target/96933] New: " linkw at gcc dot gnu.org
2020-09-04 9:33 ` linkw at gcc dot gnu.org [this message]
2020-09-04 10:26 ` [Bug target/96933] rs6000: " segher at gcc dot gnu.org
2020-09-04 10:46 ` linkw at gcc dot gnu.org
2020-09-04 12:06 ` rguenth at gcc dot gnu.org
2020-09-04 13:04 ` segher at gcc dot gnu.org
2020-09-07 2:39 ` linkw at gcc dot gnu.org
2020-09-07 7:26 ` linkw at gcc dot gnu.org
2020-09-07 15:14 ` segher at gcc dot gnu.org
2020-09-08 5:26 ` linkw at gcc dot gnu.org
2020-09-08 18:30 ` segher at gcc dot gnu.org
2020-09-09 5:20 ` linkw at gcc dot gnu.org
2020-11-05 8:09 ` cvs-commit at gcc dot gnu.org
2020-11-05 8:42 ` linkw at gcc dot gnu.org
2020-11-06 22:14 ` cvs-commit 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-96933-4-9Ha0To7K1E@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).