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 target/57202] Please make the intrinsics headers like immintrin.h be usable without compiler flags
Date: Wed, 08 May 2013 07:36:00 -0000 [thread overview]
Message-ID: <bug-57202-4-KW11FKeBT4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57202-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|x86_64-*-* i?86-*-* arm-*-* |x86_64-*-* i?86-*-*
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-05-08 07:35:52 UTC ---
(In reply to comment #1)
> This also applies to arm_neon.h.
Please file a bug separate for arm.
next prev parent reply other threads:[~2013-05-08 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 4:28 [Bug other/57202] New: " thiago at kde dot org
2013-05-08 7:03 ` [Bug target/57202] " thiago at kde dot org
2013-05-08 7:36 ` pinskia at gcc dot gnu.org [this message]
2014-02-12 15:24 ` thiago at kde dot org
2014-02-12 15:45 ` 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-57202-4-KW11FKeBT4@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).