public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/112643] [14 regression] including x86intrin.h is broken for -march=native
Date: Tue, 21 Nov 2023 17:20:22 +0000 [thread overview]
Message-ID: <bug-112643-4-ydNTK1XCyC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112643-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112643
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[14 regression] failure to |[14 regression] including
|build libitm with |x86intrin.h is broken for
|--disable-bootstrap after |-march=native
|r14-5607-g2f8f7ee2db82a3 |
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-11-21
--- Comment #18 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Ok, I am able to reproduce the issue now.
Simple testcase:
```
#include <x86intrin.h>
```
And then compile with `-march=native` and you will see the failure.
next prev parent reply other threads:[~2023-11-21 17:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:52 [Bug bootstrap/112643] New: Failure to build libitm with --disable-bootstrap after r14-5607-g2f8f7ee2db82a3 anlauf at gcc dot gnu.org
2023-11-20 20:54 ` [Bug bootstrap/112643] " anlauf at gcc dot gnu.org
2023-11-20 20:57 ` anlauf at gcc dot gnu.org
2023-11-21 3:13 ` jvdelisle at gcc dot gnu.org
2023-11-21 5:53 ` haochen.jiang at intel dot com
2023-11-21 5:59 ` sjames at gcc dot gnu.org
2023-11-21 7:00 ` urs at akk dot org
2023-11-21 7:07 ` pinskia at gcc dot gnu.org
2023-11-21 7:22 ` anlauf at gcc dot gnu.org
2023-11-21 7:28 ` pinskia at gcc dot gnu.org
2023-11-21 7:29 ` [Bug bootstrap/112643] [14 regression] failure " pinskia at gcc dot gnu.org
2023-11-21 7:30 ` haochen.jiang at intel dot com
2023-11-21 7:34 ` urs at akk dot org
2023-11-21 7:40 ` pinskia at gcc dot gnu.org
2023-11-21 7:43 ` pinskia at gcc dot gnu.org
2023-11-21 7:44 ` haochen.jiang at intel dot com
2023-11-21 7:45 ` pinskia at gcc dot gnu.org
2023-11-21 8:44 ` haochen.jiang at intel dot com
2023-11-21 9:57 ` pinskia at gcc dot gnu.org
2023-11-21 17:20 ` pinskia at gcc dot gnu.org [this message]
2023-11-21 17:22 ` [Bug target/112643] [14 regression] including x86intrin.h is broken for -march=native (which adds -mno-avx10.1-256 ) pinskia at gcc dot gnu.org
2023-11-21 17:37 ` pinskia at gcc dot gnu.org
2023-11-22 1:54 ` haochen.jiang at intel dot com
2023-11-22 7:17 ` haochen.jiang at intel dot com
2023-11-22 9:02 ` haochen.jiang at intel dot com
2023-11-23 6:10 ` haochen.jiang at intel dot com
2023-11-23 7:25 ` urs at akk dot org
2023-11-23 18:36 ` anlauf at gcc dot gnu.org
2023-11-24 2:02 ` cvs-commit at gcc dot gnu.org
2023-11-24 16:41 ` sjames 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-112643-4-ydNTK1XCyC@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).