Hi,
nice work.
On 8. 6. 2018 0:46, J. Gareth Moreton wrote:
> The deep optimiser changes this to:
>
> movq %rcx,%rax
> movq %rdx,%rsi
> movq %rcx,%rbx
>
> It determines, for the third MOV, it can
> change %rax for %rcx to minimise a
> pipeline stall, and then knows that %rbx
> and %rcx conta
Hi,
On 17. 5. 2018 0:56, Wolf wrote:
>
>
> On 14/05/2018 04:30, David Pethes wrote:
>> Hi,
>> I would welcome inlining of (simple) asm routines.
>>
> I do not know what you consider to be the existing obstacles to inlining
> assembler routines.
That this doesn
Hi,
I would welcome inlining of (simple) asm routines. Lately I wanted to
use the BEXTR instruction to speed up some inlined bit reading
functions. As there's no intrinsic for it and including even a simple
assembly method disables inlining, it didn't go well.
As for using a BEXTR intrinsic instea
Graeme Geldenhuys wrote:
PS:
The image was received fine. I noticed with my own experimentation
that small screenshots (not photos) work better as GIF images. It's a
much better option for size reduction with no visual loss. Your image
as PNG is 28K. As a GIF it's only 17.5K
:-) Don't use JPG's,
Graeme Geldenhuys wrote:
Is assembler code generated for a call to a blank (no content)
procedure? The content of the procedure might be IFDEF'd out.
I've checked it, and it does. Mark the procedure as inline together with
IFDEF-ing its code, and there will be no overhead.
David
___
