<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 29 Nov 2012, at 13:00, Anton Kavalenka wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; "><a href="http://bugs.freepascal.org/view.php?id=18079">http://bugs.freepascal.org/view.php?id=18079</a><br>now closed<br><br>I've just tested latest SVN trunk (Revision: 23078) and still get 5000 ms<br><br>What define should i pass building the compiler to achieve same performance as i386 (300 msec)?<br></span></span></blockquote></div><br><div>The title of your mail is wrong: the assembler move implementation /is/ enabled by default on x86-64 now. The other problem is some bad behaviour by the memory manager apparently, but I am unable to reproduce it anywhere.</div><div><br></div><div><br></div><div>Jonas</div></body></html>