Re: -march=x86-64 (was: illegal instruction (CPU mismatch))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx>, Jeffrey Walton <noloader@xxxxxxxxx>
Subject: Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
Date: Sun, 18 Sep 2016 11:02:32 +0000 (UTC)
Cc: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>, Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
In-reply-to: <alpine.DEB.2.20.1609181117440.3998@laptop-mg.saclay.inria.fr>
References: <CAH8yC8mmWZkVr1UvEKfv0XzwnDbYNCcCxc8974d5oNQ6UHBobQ@mail.gmail.com> <alpine.DEB.2.20.1609181117440.3998@laptop-mg.saclay.inria.fr>
Reply-to: Mahmood Naderan <nt_mahmood@xxxxxxxxx>

> That switch caught my eye because its the opposite of -mach=native


Hi Jeffery,
Actually I didn't understand. Do you mean that -march=x86-64 is an invalid option?


 Regards,
Mahmood

Follow-Ups:
- Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  - From: Markus Trippelsdorf

References:
- -march=x86-64 (was: illegal instruction (CPU mismatch))
  - From: Jeffrey Walton
- Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  - From: Marc Glisse

Prev by Date: Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
Next by Date: Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
Previous by thread: Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
Next by thread: Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux