diff options
| author | Peter Collingbourne <pcc@google.com> | 2013-05-15 20:31:53 +0200 |
|---|---|---|
| committer | Andreas Jaeger <aj@suse.de> | 2013-05-15 20:31:53 +0200 |
| commit | 791f3ba0db02911933255d080b8ff973330b9ebf (patch) | |
| tree | 7d54d11ba341791af9dbf0e94d5cfeda98c78694 /csu | |
| parent | 39b1f6172a2f9ddc74a8f82d6e84dd13b22dbaf2 (diff) | |
| download | glibc-791f3ba0db02911933255d080b8ff973330b9ebf.tar glibc-791f3ba0db02911933255d080b8ff973330b9ebf.tar.gz glibc-791f3ba0db02911933255d080b8ff973330b9ebf.tar.bz2 glibc-791f3ba0db02911933255d080b8ff973330b9ebf.zip | |
Use x constraints for operands to vfmaddss and vfmaddsd
While these instructions accept memory operands, only one operand
may be a memory operand. Giving two operands xm constraints gives
the compiler the option of using memory for both operands, which
would result in invalid assembly code. Using x for all operands is
more appropriate, as most x86_64 calling conventions will pass the
arguments in registers anyway.
2013-05-15 Peter Collingbourne <pcc@google.com>
* sysdeps/x86_64/fpu/multiarch/s_fma.c (__fma_fma4): Replace xm
constraints with x constraints.
* sysdeps/x86_64/fpu/multiarch/s_fmaf.c (__fmaf_fma4): Likewise.
Diffstat (limited to 'csu')
0 files changed, 0 insertions, 0 deletions