public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/49128] gcc -mtune=native generates unsuported instructions Date: Mon, 23 May 2011 17:32:00 -0000 [thread overview] Message-ID: <bug-49128-4-ZgbHNOiTLB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49128-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49128 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-05-23 16:53:00 UTC --- you haven't provided the necessary information requested at http://gcc.gnu.org/bugs/ Specifically you need to say how your gcc was configured (because -mtune should not affect the instructions gcc thinks are supported, that's set by -march) and provide your full compilation command and example code which reproduces the problem
next prev parent reply other threads:[~2011-05-23 17:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-23 16:47 [Bug c/49128] New: gcc -mtune=native generates unsoported instructions nathanael.schaeffer+ml at gmail dot com 2011-05-23 17:32 ` redi at gcc dot gnu.org [this message] 2011-05-23 18:55 ` [Bug c/49128] -mtune=native generates unsupported instructions hjl.tools at gmail dot com 2011-05-23 21:08 ` nathanael.schaeffer+ml at gmail dot com 2011-05-23 21:11 ` nathanael.schaeffer+ml at gmail dot com 2011-05-24 17:59 ` [Bug c/49128] -march=native " hjl at gcc dot gnu.org 2011-05-24 18:11 ` hjl at gcc dot gnu.org 2011-05-24 18:16 ` hjl.tools at gmail dot com 2011-05-25 6:53 ` Joost.VandeVondele at pci dot uzh.ch 2011-05-25 7:33 ` jakub at gcc dot gnu.org 2011-05-25 11:57 ` Joost.VandeVondele at pci dot uzh.ch 2011-05-25 12:44 ` jakub at gcc dot gnu.org 2011-05-25 13:31 ` Joost.VandeVondele at pci dot uzh.ch
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-49128-4-ZgbHNOiTLB@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).