public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54427] Expose more vector extensions
Date: Fri, 14 Sep 2012 17:22:00 -0000	[thread overview]
Message-ID: <bug-54427-4-Te51JzRfu6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54427-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54427

--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> 2012-09-14 17:22:24 UTC ---
Progress :-)

Documentation update is needed.

Next useful one would be ?: so we can generate vec_cond_expr. See the OpenCL
specification for a list of what's missing.

Another useful thing would be to audit the optimization passes that don't
expect vectors and mishandle them...


  parent reply	other threads:[~2012-09-14 17:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 20:07 [Bug c++/54427] New: " glisse at gcc dot gnu.org
2012-09-03 10:38 ` [Bug c++/54427] " rguenth at gcc dot gnu.org
2012-09-14 17:17 ` glisse at gcc dot gnu.org
2012-09-14 17:22 ` glisse at gcc dot gnu.org [this message]
2012-09-20 19:01 ` pthaugen at gcc dot gnu.org
2012-09-20 19:13 ` pthaugen at gcc dot gnu.org
2012-09-20 19:47 ` glisse at gcc dot gnu.org
2012-09-21  9:20 ` glisse at gcc dot gnu.org
2012-09-27 10:06 ` glisse at gcc dot gnu.org
2012-10-09  6:18 ` glisse at gcc dot gnu.org
2012-10-25 13:03 ` glisse at gcc dot gnu.org
2012-10-25 13:17 ` glisse at gcc dot gnu.org
2013-04-12 13:59 ` glisse at gcc dot gnu.org
2013-05-07 21:59 ` glisse at gcc dot gnu.org
2013-09-14 21:42 ` glisse at gcc dot gnu.org
2013-11-10  8:56 ` glisse at gcc dot gnu.org
2014-10-03 19:57 ` glisse at gcc dot gnu.org
2014-10-03 20:21 ` glisse 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-54427-4-Te51JzRfu6@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).