public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56038] declarations in xmmintrin.h conflict with mingw-w64 intrin.h in c++ mode
Date: Fri, 20 Sep 2013 16:08:00 -0000 [thread overview]
Message-ID: <bug-56038-4-NLdJChld7h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56038-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56038
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #9)
> Does mingw provide its own SSE/MMX intrinsic implementations?
> Can mingw just include <xmmintrin.h> where SSE/MMX instrincis
> is needed?
Right. Why does mingw need to declare these functions itself?
next prev parent reply other threads:[~2013-09-20 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 22:05 [Bug c++/56038] New: " erik-gcc-bugzilla at vanpienbroek dot nl
2013-02-15 10:41 ` [Bug c++/56038] " kretz at kde dot org
2013-03-25 4:12 ` net147 at gmail dot com
2013-03-25 10:38 ` net147 at gmail dot com
2013-03-26 12:26 ` kai.koehne at digia dot com
2013-06-10 8:37 ` kai.koehne at digia dot com
2013-09-20 7:29 ` vanboxem.ruben at gmail dot com
2013-09-20 14:36 ` jacek at codeweavers dot com
2013-09-20 15:35 ` hjl.tools at gmail dot com
2013-09-20 16:08 ` jason at gcc dot gnu.org [this message]
2014-03-22 15:34 ` tim.lebedkov at gmail dot com
2014-03-23 19:17 ` erik-gcc-bugzilla at vanpienbroek dot nl
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-56038-4-NLdJChld7h@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).