public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sascha-web-gcc dot gnu dot org at silbe dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37179] gcc emits bad opcode 'ffreep' Date: Sun, 10 May 2009 10:07:00 -0000 [thread overview] Message-ID: <20090510100733.5793.qmail@sourceware.org> (raw) In-Reply-To: <bug-37179-2749@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-10 10:07 ------- > /* X86_TUNE_USE_FFREEP */ > m_AMD_MULTIPLE, Without having dug into the source, I'd guess that this is the exact location of the bug. > #define m_AMD_MULTIPLE (m_K8 | m_ATHLON | m_AMDFAM10) If AMDFAM10 is the AMD Geode series of processors and all of them don't support ffreep (needs checking), then the above line should read /* X86_TUNE_USE_FFREEP */ (m_K8 | m_ATHLON), instead. The bug indeed seems only to happen for -march=native (haven't tested anything besides native yet), BTW. I.e. if you don't specify an architecture at all, ffreep won't get issued. -- sascha-web-gcc dot gnu dot org at silbe dot org changed: What |Removed |Added ---------------------------------------------------------------------------- GCC build triplet|vortex86-pc-linux | GCC target triplet|vortex86-pc-linux | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37179
next prev parent reply other threads:[~2009-05-10 10:07 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-20 19:17 [Bug c/37179] New: " ebuddington at wesleyan dot edu 2008-08-20 19:19 ` [Bug target/37179] " pinskia at gcc dot gnu dot org 2008-08-20 19:20 ` pinskia at gcc dot gnu dot org 2008-08-20 19:20 ` pinskia at gcc dot gnu dot org 2009-05-07 17:54 ` sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-07 18:00 ` sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-07 20:37 ` ubizjak at gmail dot com 2009-05-10 10:07 ` sascha-web-gcc dot gnu dot org at silbe dot org [this message] 2009-05-10 14:28 ` ubizjak at gmail dot com 2009-05-10 17:12 ` sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-10 17:51 ` ubizjak at gmail dot com 2009-05-10 18:05 ` sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-10 20:56 ` ubizjak at gmail dot com 2009-05-10 21:22 ` sascha-web-gcc dot gnu dot org at silbe dot org 2009-05-10 22:00 ` ubizjak at gmail dot com 2009-05-12 12:08 ` ubizjak at gmail dot com 2009-05-12 16:33 ` hjl at gcc dot gnu dot org 2009-05-13 10:06 ` uros at gcc dot gnu dot org 2009-05-14 8:23 ` uros at gcc dot gnu dot org 2009-05-14 8:25 ` ubizjak at gmail dot com
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=20090510100733.5793.qmail@sourceware.org \ --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).