public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98860] boostrap failure on MinGW-w64 windows 10 Date: Thu, 28 Jan 2021 02:40:43 +0000 [thread overview] Message-ID: <bug-98860-4-NOt1j9UrXr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98860-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #5 from cqwrteur <unlvsur at live dot com> --- I do not know whether it has to do with the CRLF issue because GCC on Linux emits the same result as it does on MinGW-w64 or msys2. conftextx.c #ifdef __x86_64__ #ifndef __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 #error need -march=i486 #endif #ifndef __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 #error need -mcx16 #endif #else #ifndef __GCC_HAVE_SYNC_COMPARE_AND_SWAP_8 #error need -march=i686 #endif #endif MinGW32 unlvs@DESKTOP-DFHPDC1 MINGW32 ~/gcc_bug $ gcc -E conftestx.c # 1 "conftestx.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "conftestx.c" unlvs@DESKTOP-DFHPDC1 MINGW32 ~/gcc_bug $ gcc -E conftestx.c -march=i486 # 1 "conftestx.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "conftestx.c" conftestx.c:10:2: error: #error need -march=i686 10 | #error need -march=i686 | ^~~~~ MinGW64 unlvs@DESKTOP-DFHPDC1 MINGW64 ~/gcc_bug $ gcc -E conftestx.c -m32 # 1 "conftestx.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "conftestx.c" unlvs@DESKTOP-DFHPDC1 MINGW64 ~/gcc_bug $ gcc -E conftestx.c -march=i486 -mtune=generic # 1 "conftestx.c" cc1.exe: error: CPU you selected does not support x86-64 instruction set MSYS (which is x86_64 with CYGWIN) unlvs@DESKTOP-DFHPDC1 MSYS ~/gcc_bug $ gcc -E conftestx.c # 1 "conftestx.c" # 1 "<built-in>" # 1 "<command-line>" # 1 "conftestx.c" conftestx.c:6:2: error: #error need -mcx16 6 | #error need -mcx16 | ^~~~~ unlvs@DESKTOP-DFHPDC1 MSYS ~/gcc_bug $ gcc -E conftestx.c -march=i486 # 1 "conftestx.c" cc1: error: CPU you selected does not support x86-64 instruction set The result on Linux: cqwrteur@DESKTOP-DFHPDC1:/mnt/d/msys64/home/unlvs/gcc_bug$ gcc -E conftestx.c # 0 "conftestx.c" # 0 "<built-in>" # 0 "<command-line>" # 1 "/usr/include/stdc-predef.h" 1 3 4 # 0 "<command-line>" 2 # 1 "conftestx.c" conftestx.c:6:2: error: #error need -mcx16 6 | #error need -mcx16 | ^~~~~ cqwrteur@DESKTOP-DFHPDC1:/mnt/d/msys64/home/unlvs/gcc_bug$ gcc -E conftestx.c -march=i486 # 0 "conftestx.c" cc1: error: CPU you selected does not support x86-64 instruction set
next prev parent reply other threads:[~2021-01-28 2:40 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 22:20 [Bug bootstrap/98860] New: " unlvsur at live dot com 2021-01-27 23:10 ` [Bug bootstrap/98860] " unlvsur at live dot com 2021-01-28 0:34 ` unlvsur at live dot com 2021-01-28 0:49 ` unlvsur at live dot com 2021-01-28 2:35 ` unlvsur at live dot com 2021-01-28 2:40 ` unlvsur at live dot com [this message] 2021-01-28 7:39 ` unlvsur at live dot com 2021-01-28 7:41 ` [Bug bootstrap/98860] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-28 8:04 ` unlvsur at live dot com 2021-01-28 8:48 ` unlvsur at live dot com 2021-01-28 9:25 ` unlvsur at live dot com 2021-01-28 9:31 ` jakub at gcc dot gnu.org 2021-01-28 9:32 ` unlvsur at live dot com 2021-01-28 9:36 ` jakub at gcc dot gnu.org 2021-01-28 9:38 ` unlvsur at live dot com 2021-01-28 9:40 ` unlvsur at live dot com 2021-01-28 9:49 ` lh_mouse at 126 dot com 2021-01-28 14:32 ` unlvsur at live dot com 2021-01-28 14:35 ` jakub at gcc dot gnu.org 2021-01-28 15:36 ` unlvsur at live dot com 2021-01-28 15:48 ` unlvsur at live dot com 2021-01-29 3:44 ` lh_mouse at 126 dot com 2021-02-02 12:05 ` ebotcazou at gcc dot gnu.org 2021-02-03 12:56 ` nix at esperi dot org.uk 2021-02-03 15:27 ` nix at esperi dot org.uk 2021-02-03 15:29 ` nix at esperi dot org.uk 2021-02-06 22:08 ` mikpelinux at gmail dot com 2021-02-06 22:14 ` unlvsur at live dot com 2021-02-07 9:19 ` brechtsanders at users dot sourceforge.net 2021-02-07 17:08 ` mikpelinux at gmail dot com 2021-02-07 20:38 ` unlvsur at live dot com 2021-02-08 21:45 ` mikpelinux at gmail dot com 2021-02-09 20:22 ` mikpelinux at gmail dot com 2021-02-09 20:38 ` redi at gcc dot gnu.org 2021-02-09 20:39 ` redi at gcc dot gnu.org 2021-02-16 14:30 ` hjl.tools at gmail dot com 2021-02-26 12:38 ` rguenth at gcc dot gnu.org 2021-02-26 12:48 ` ssbssa at yahoo dot de 2021-02-26 17:55 ` jakub at gcc dot gnu.org 2021-03-01 22:05 ` [Bug bootstrap/98860] [11 Regression] bootstrap " mikpelinux at gmail dot com 2021-03-17 10:42 ` jakub at gcc dot gnu.org 2021-03-17 12:03 ` jyong at gcc dot gnu.org 2021-03-17 12:39 ` jakub at gcc dot gnu.org 2021-03-17 13:05 ` jakub at gcc dot gnu.org 2021-03-18 14:26 ` jyong at gcc dot gnu.org 2021-03-18 14:42 ` jakub at gcc dot gnu.org 2021-03-23 14:02 ` jakub at gcc dot gnu.org 2021-03-23 14:54 ` jyong at gcc dot gnu.org 2021-03-23 15:09 ` jakub at gcc dot gnu.org 2021-03-23 15:43 ` jyong at gcc dot gnu.org 2021-03-23 16:02 ` jakub at gcc dot gnu.org 2021-03-23 16:12 ` jyong at gcc dot gnu.org 2021-03-23 17:12 ` jyong at gcc dot gnu.org 2021-03-23 17:59 ` jyong at gcc dot gnu.org 2021-03-23 18:16 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-24 13:44 ` jyong at gcc dot gnu.org 2021-03-24 19:31 ` rogero at howzatt dot co.uk 2021-03-31 7:12 ` cvs-commit at gcc dot gnu.org 2021-03-31 7:13 ` jakub at gcc dot gnu.org 2021-03-31 13:42 ` jyong 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-98860-4-NOt1j9UrXr@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: linkBe 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).