public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pageexec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/59335] Plugin doesn't build on trunk
Date: Sun, 26 Jan 2014 23:34:00 -0000 [thread overview]
Message-ID: <bug-59335-4-R3uRYLaarU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59335-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59335
--- Comment #8 from PaX Team <pageexec at gmail dot com> ---
Uroš, i tried your patch and it didn't install those two files. on the other
hand i found more missing headers:
gcc/tree-phinodes.h
gcc/stor-layout.h
gcc/ssa-iterators.h
>From gcc-bugs-return-441583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 27 05:03:49 2014
Return-Path: <gcc-bugs-return-441583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13626 invoked by alias); 27 Jan 2014 05:03:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13603 invoked by uid 48); 27 Jan 2014 05:03:44 -0000
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59952] New: -march=core-avx2 should not enable RTM
Date: Mon, 27 Jan 2014 05:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thiago at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-59952-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg02725.txt.bz2
Content-length: 1863
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY952
Bug ID: 59952
Summary: -march=core-avx2 should not enable RTM
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: thiago at kde dot org
The option -march=core-avx2 to gcc is documented to enable:
Intel Core CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2,
SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AES, PCLMUL,
FSGSBASE, RDRND, FMA, BMI, BMI2 and F16C instruction set
support.
However, it is enabling RTM (Restricted Transactional Memory) too:
$ ~/gcc4.9/bin/g++-4.9 -march=core-avx2 -dM -E -xc /dev/null | grep RTM
#define __RTM__ 1
$ ~/gcc4.9/bin/g++-4.9 --version
g++-4.9 (GCC) 4.9.0 20140125 (experimental)
Only certain Haswell processors have TSX in either form in the CPU. The mobile
parts don't:
$ sed -n '/name/p;/flags/p;/^$/q' /proc/cpuinfo
model name : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2
ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2
erms invpcid
According to the source code, HLE is enabled too when it shouldn't:
#define PTA_HASWELL \
(PTA_IVYBRIDGE | PTA_AVX2 | PTA_BMI | PTA_BMI2 | PTA_LZCNT \
| PTA_FMA | PTA_MOVBE | PTA_RTM | PTA_HLE)
next prev parent reply other threads:[~2014-01-26 23:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 3:00 [Bug plugins/59335] New: " joey.ye at arm dot com
2013-11-29 3:34 ` [Bug plugins/59335] " pinskia at gcc dot gnu.org
2014-01-10 17:54 ` sje at gcc dot gnu.org
2014-01-10 17:56 ` sje at gcc dot gnu.org
2014-01-11 1:20 ` pageexec at gmail dot com
2014-01-11 13:01 ` ubizjak at gmail dot com
2014-01-26 23:34 ` pageexec at gmail dot com [this message]
2014-02-13 5:51 ` joey.ye at arm dot com
2014-02-13 11:31 ` pageexec at gmail dot com
2014-02-14 1:29 ` joey.ye at arm dot com
2014-02-18 15:02 ` pageexec at gmail dot com
2014-03-04 13:48 ` pageexec at gmail dot com
2014-03-05 9:52 ` jakub at gcc dot gnu.org
2014-03-05 15:07 ` jakub at gcc dot gnu.org
2014-03-05 21:29 ` jakub at gcc dot gnu.org
2014-03-05 22:47 ` pageexec at gmail dot com
2014-04-13 20:04 ` pageexec at gmail dot com
2014-04-13 20:46 ` ubizjak at gmail dot com
2014-04-14 7:48 ` jakub at gcc dot gnu.org
2014-04-14 9:43 ` jakub at gcc dot gnu.org
2014-04-14 9:49 ` pageexec at gmail dot com
2014-04-14 10:02 ` jakub at gcc dot gnu.org
2014-04-15 8:03 ` jakub at gcc dot gnu.org
2014-04-15 8:04 ` jakub at gcc dot gnu.org
2014-04-15 8:10 ` jakub at gcc dot gnu.org
2014-08-25 2:16 ` terry.guo at arm dot com
2014-08-25 2:17 ` joey.ye at arm dot com
2014-09-05 6:52 ` jye2 at gcc dot gnu.org
2014-09-05 6:56 ` joey.ye at arm dot com
2021-08-28 4:18 ` pinskia 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-59335-4-R3uRYLaarU@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).