Re: user-defined alignment in gfortran

Richard Maine <nospam@xxxxxxxxxxxxx> schrieb:
glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx> wrote:

No hardware that I know of has instruction that operate on
complex data. There is no complex add or complex multiply
instruction. Operations are done on separate real and imaginary
parts using ordinary floating point instructions.

Reread the original post. He was not talking about Fortran operations on
the complex data. He specifically cited DMA transfer as the reason for
the request and he said it was a specific array. Doesn't sound to me as
though it directly had anything to do with it being complex, but just
that this particular array was the one involved withthe DMA transfer.

Yes! I dont care about the type of the array, I just want the array to
be 16-byte aligned.

Regards,
Timo
.

Relevant Pages

  • Re: user-defined alignment in gfortran
    ... instruction. ... the complex data. ... that this particular array was the one involved withthe DMA transfer. ...
    (comp.lang.fortran)
  • Re: user-defined alignment in gfortran
    ... instruction. ... the complex data. ... that this particular array was the one involved withthe DMA transfer. ... Start with the assumption that dynamic allocation will give you an address that is eight-byte aligned, so figure out how many real*8 elements you need, and add one. ...
    (comp.lang.fortran)
  • Re: user-defined alignment in gfortran
    ... instruction. ... the complex data. ... that this particular array was the one involved withthe DMA transfer. ... similar in Fortran, although you might give up some portability. ...
    (comp.lang.fortran)
  • Re: sub esp, 0ch question
    ... No, if it was a char array, the length would be 192. ... The rep stos ... rep stos instruction does this all in one shot as opposed to setting ... that Debug builds have a minimum local stack size so that recursion ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Looping through array, deleting elements
    ... instruction has two attributes, parm and arg. ... the loop is looking at element x foo, ... foo get's deleted, the array is shifted left, array pointer has not ... and now array pointer is pointing at element z foo. ...
    (comp.lang.ruby)