public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59952] -march=core-avx2 should not enable RTM
Date: Mon, 27 Jan 2014 18:21:00 -0000 [thread overview]
Message-ID: <bug-59952-4-X03xlEWVpA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59952-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59952
--- Comment #5 from Mikael Pettersson <mikpelinux at gmail dot com> ---
(In reply to Thiago Macieira from comment #4)
> (In reply to Mikael Pettersson from comment #3)
> > There are also Haswells that lack BMI2. I updated our dynamic binary
> > instrumentation engine for AVX2 about a year ago, but while our Haswell box
> > at the time had AVX2 it didn't have BMI2 etc, causing Intel's MKL to refuse
> > to enter it AVX2 code paths. So testing had to be limited to small
> > assembly-coded kernels.
>
> Are you sure? Unfortunately, ark.intel.com does not list BMI instruction
> level.
Yes I'm sure. According to my notes the processor was a 2.0 GHz 4c/8t
i7-4765T. It may have been an engineering sample, this was at my previous job
and I can't access the machine any more.
next prev parent reply other threads:[~2014-01-27 18:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-59952-4@http.gcc.gnu.org/bugzilla/>
2014-01-27 7:50 ` jakub at gcc dot gnu.org
2014-01-27 9:00 ` thiago at kde dot org
2014-01-27 9:23 ` mikpelinux at gmail dot com
2014-01-27 15:11 ` thiago at kde dot org
2014-01-27 18:21 ` mikpelinux at gmail dot com [this message]
2014-01-27 18:27 ` jakub at gcc dot gnu.org
2014-01-27 18:38 ` thiago at kde dot org
2014-01-27 18:54 ` thiago at kde dot org
2014-01-27 19:11 ` kirill.yukhin at intel dot com
2014-01-27 19:53 ` thiago at kde dot org
2014-01-31 14:01 ` kirill.yukhin at intel dot com
2014-05-08 5:17 ` thiago at kde dot org
2014-05-08 16:29 ` ubizjak at gmail dot com
2014-05-08 16:57 ` hjl.tools at gmail dot com
2014-05-08 17:11 ` ubizjak at gmail dot com
2014-05-08 17:18 ` jakub at gcc dot gnu.org
2014-05-08 17:20 ` ubizjak at gmail dot com
2014-05-08 18:06 ` thiago at kde dot org
2014-05-08 19:01 ` ubizjak at gmail dot com
2014-05-08 19:13 ` uros at gcc dot gnu.org
2014-05-08 19:24 ` uros at gcc dot gnu.org
2014-05-08 19:33 ` uros at gcc dot gnu.org
2014-05-08 19:34 ` ubizjak at gmail dot com
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-59952-4-X03xlEWVpA@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).