public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/57202] New: Please make the intrinsics headers like immintrin.h be usable without compiler flags
Date: Wed, 08 May 2013 04:28:00 -0000	[thread overview]
Message-ID: <bug-57202-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 57202
           Summary: Please make the intrinsics headers like immintrin.h be
                    usable without compiler flags
    Classification: Unclassified
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: thiago@kde.org


Please make all headers for intrinsics be includable without special compiler
flags.

In other words, I want the following to work:

$ gcc -fsyntax-only -include smmintrin.h -xc /dev/null
In file included from <command-line>:0:0:
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/include/smmintrin.h:31:3: error: #error
"SSE4.1 instruction set not enabled"

Note it works with ICC:
$ icc -fsyntax-only -include smmintrin.h -xc /dev/null && echo works
works


Not only that, please make all the intrinsics functions be defined and ready to
be used.

This is necessary so that the following source file could compile even if
-msse4.1 is not passed on the command-line (adapted from
http://gcc.gnu.org/gcc-4.8/changes.html):

#include <smmintrin.h>

 __attribute__ ((target ("default")))
int foo(void)
{
  return 1;
}

__attribute__ ((target ("sse4.2")))
int foo(void)
{
  __m128i v;
  _mm_blendv_epi8(v, v, v);
  return 2;
}

There are several reasons for that, number one among them that it makes the GCC
4.8 feature above actually useful for non-trivial code. Also, passing extra
options on the command-line are simply not an option for C++ code (where the
feature above is useful) if that code is moderately complex and uses inline
functions, and those options cannot be used if LTO is to be used (bug 54231).


             reply	other threads:[~2013-05-08  4:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08  4:28 thiago at kde dot org [this message]
2013-05-08  7:03 ` [Bug target/57202] " thiago at kde dot org
2013-05-08  7:36 ` pinskia at gcc dot gnu.org
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@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).