To get back on track with uComplex, I didn't change any routines to make
them inline - they were that way already. All I did was change the
parameters to 'const', align the complex type so it is equivalent to
__m128d so the System V ABI can pass it all in one register, and enable
vectorcall
Am 31.10.19 um 20:11 schrieb Marco van de Voort:
Op 2019-10-30 om 23:02 schreef Florian Klämpfl:
Yes. And manually adding inline is only as good as the knowledge of
the user doing so. If somebody implements it right (I did not, I used
the easiest approach and used an existing function to
Op 2019-10-30 om 23:02 schreef Florian Klämpfl:
Yes. And manually adding inline is only as good as the knowledge of
the user doing so. If somebody implements it right (I did not, I used
the easiest approach and used an existing function to estimate the
complexity of a subroutine). The
Hi,
I just created a bug report (
https://bugs.freepascal.org/view.php?id=36236 ) for this .
regards,
--
Dimitrios Chr. Ioannidis
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
I forgot about "fullcycle", thanks. The main reason is because of the
"condition_in" functions I've added to the other platforms - I want to
see if they at least compile!
Now the fun begins.
Gareth aka. Kit
On 31/10/2019 06:18, Sven Barth via fpc-devel wrote:
Am 31.10.2019 um 05:57 schrieb
Am 31.10.2019 um 05:57 schrieb J. Gareth Moreton:
One thing I do need to do is to cross-compile to all known
platforms... I can only test a handful of the i386 and x86_64
platforms, but I want to at least see if it compiles before I submit
the patch for more thorough testing. Does anyone have
