From: Tim Prince <timothyprince@sbcglobal.net>
To: Brian Budge <brian.budge@gmail.com>
Cc: Matthieu Godet <matthieu.godet.work@hotmail.com>, gcc-help@gcc.gnu.org
Subject: Re: mmx/sse builtins
Date: Wed, 28 Jun 2006 15:56:00 -0000 [thread overview]
Message-ID: <44A2A692.5060700@sbcglobal.net> (raw)
In-Reply-To: <5b7094580606280833x1a06ec21pe47abf2577e04606@mail.gmail.com>
Brian Budge wrote:
> A most excellent question. I'd like to add my own on top of that: It
> appears that with 4.1.x, the xmmintrin.h, pmmintrin.h, etc... are
> missing. Will they be back?
>
If you mean you've noticed the tendency of gcc programmers to use
alternates for code which requires data types from those headers when
compiled with commercial compilers, I doubt the trend will reverse.
As those headers appear in my gcc-4.2 installations, I don't think you
mean you suspect they will be removed from gcc.
next prev parent reply other threads:[~2006-06-28 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 13:19 Matthieu Godet
2006-06-28 15:33 ` Brian Budge
2006-06-28 15:56 ` Tim Prince [this message]
2006-06-28 16:24 ` Brian Budge
2006-06-28 19:41 ` Ian Lance Taylor
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=44A2A692.5060700@sbcglobal.net \
--to=timothyprince@sbcglobal.net \
--cc=brian.budge@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=matthieu.godet.work@hotmail.com \
--cc=tprince@myrealbox.com \
/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).