public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/55457] Having some predefined macros to get more information about gcc vector extensions capabilities would be nice
Date: Sun, 09 Dec 2012 01:39:00 -0000	[thread overview]
Message-ID: <bug-55457-4-5cJMvaKqQq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55457-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-09 01:39:39 UTC ---
The whole point of the gcc vector extensions is that you don't need to depend
on what the hardware can do under neath as it should produce good code in
either case.


  reply	other threads:[~2012-12-09  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 16:13 [Bug c/55457] New: " siarhei.siamashka at gmail dot com
2012-12-09  1:39 ` pinskia at gcc dot gnu.org [this message]
2012-12-09  2:33 ` [Bug c/55457] " siarhei.siamashka at gmail dot com
2012-12-09 23:03 ` hp 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-55457-4-5cJMvaKqQq@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).