This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/37179] gcc emits bad opcode 'ffreep'
- From: "sascha-web-gcc dot gnu dot org at silbe dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 May 2009 10:07:33 -0000
- Subject: [Bug target/37179] gcc emits bad opcode 'ffreep'
- References: <bug-37179-2749@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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