------- Comment #1 from markusl dot se78 at gmail dot com 2009-12-28 17:59
-------
Another solution might be to have a define_insn_and_split for a 64x64->64bit
multiply allowing the combiner to do its job combining into a widening
multiplication and if this fails the insn will later be split into the double
word multiply sequence. Anyway this is what I had in mind for fixing the same
issue with a private port (based on gcc 4.4.1). Are there any obvious drawbacks
of such an approach (besides that it is local and needs to be applied for every
target that sees the problem)?
--
markusl dot se78 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markusl dot se78 at gmail
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42498
