- 05 Nov, 2012 1 commit
-
-
Diego Biurrun authored
-
- 02 Nov, 2012 4 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
Diego Biurrun authored
"mmxext" is a more sensible name and more common in outside projects.
-
Diego Biurrun authored
This allows overriding the value from outside of the file.
-
- 31 Oct, 2012 3 commits
-
-
Dave Yeo authored
Unlike YASM, NASM only looks for include files in the current directory, not in the directory that included files reside in. Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
Dave Yeo authored
Unlike YASM, NASM only looks for include files in the current directory, not in the directory that included files reside in. Signed-off-by:
Diego Biurrun <diego@biurrun.de>
-
Diego Biurrun authored
-
- 30 Oct, 2012 1 commit
-
-
Diego Biurrun authored
This is necessary to allow refactoring some x86util macros with cpuflags.
-
- 29 Oct, 2012 1 commit
-
-
Ronald S. Bultje authored
-
- 04 Oct, 2012 5 commits
-
-
Diego Biurrun authored
ff_get_cpu_flags_x86() requires cpuid(), which is conditionally defined elsewhere in the file. Surrounding the function body with ifdefs allows building even when cpuid is not defined. An empty cpuflags mask is returned in this case.
-
Diego Biurrun authored
Now that there is CPU detection in YASM, there will always be one of inline or external assembly enabled, which obviates the need to fall back on CPU detection through compiler intrinsics.
-
Diego Biurrun authored
This allows detecting CPU features with builds that have neither gcc inline assembly nor the right compiler intrinsics enabled.
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 08 Sep, 2012 1 commit
-
-
Diego Biurrun authored
This separates code relying on inline from that relying on external assembly and fixes instances where the coalesced check was incorrect.
-
- 07 Sep, 2012 1 commit
-
-
Justin Ruggles authored
The SWAP macro does not work for explicit xmm/ymm usage, so instead just move the scalar value from xmm2 to xmm0.
-
- 03 Sep, 2012 1 commit
-
-
Diego Biurrun authored
-
- 01 Sep, 2012 1 commit
-
-
Carl Eugen Hoyos authored
-
- 30 Aug, 2012 2 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 26 Aug, 2012 1 commit
-
-
Loren Merritt authored
13% faster on penryn, 16% on sandybridge, 15% on bulldozer Not simd; a compiler should have generated this, but gcc didn't.
-
- 24 Aug, 2012 1 commit
-
-
Justin Ruggles authored
-
- 22 Aug, 2012 1 commit
-
-
Mans Rullgard authored
GCC 4.3 and later do the right thing with the plain C code. Earlier versions in 32-bit mode generate one extra instruction, needlessly zeroing what would be the high half of the shifted value. At least two gcc configurations miscompile the inline asm in some situations. In 64-bit mode, all gcc versions generate imul r64, r64 followed by shr. On Intel i7 and later, this imul is faster 32-bit mul. On older Intel and all AMD, it is slightly slower. On Atom it is much slower. Considering where the FASTDIV macro is used, any overall negative performance impact of this change should be negligible. If anyone cares, they should file a bug against gcc and get the instruction selection fixed. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
- 16 Aug, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 15 Aug, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 08 Aug, 2012 2 commits
-
-
Mans Rullgard authored
These x86-specific macros do not belong in generic code. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
This puts x86-specific things in the x86/ subdirectory where they belong. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
- 07 Aug, 2012 5 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Mans Rullgard authored
It appears that something goes wrong in old nasm versions when the %+ operator is used in the last argument of a macro invocation and this argument is tested with %ifdef within the macro. This patch rearranges the macro arguments such that the %+ operator is never used in the last argument.
-
Mans Rullgard authored
nasm does not support 'CPU foonop' directives. This adds a configure test for the directive and uses it only if supported. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
For some reason, nasm requires this. No harm done to yasm. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
nasm prints a warning if the colon is missing. Signed-off-by:
Mans Rullgard <mans@mansr.com>
-
- 03 Aug, 2012 2 commits
-
-
Diego Biurrun authored
Refactoring mmx2/mmxext YASM code with cpuflags will force renames. So switching to a consistent naming scheme beforehand is sensible. The name "mmxext" is more official and widespread and also the name of the CPU flag, as reported e.g. by the Linux kernel.
-
Diego Biurrun authored
Currently there is a wild mix of 3dn2/3dnow2/3dnowext. Switching to "3dnowext", which is a more common name of the CPU flag, as reported e.g. by the Linux kernel, unifies this.
-
- 28 Jul, 2012 2 commits
-
-
Loren Merritt authored
This allows us to unconditionally set the cglobal num_args parameter to a bigger value, thus making writing yasm code even easier than before. Signed-off-by:
Ronald S. Bultje <rsbultje@gmail.com>
-
Ronald S. Bultje authored
-
- 27 Jul, 2012 1 commit
-
-
Justin Ruggles authored
-
- 26 Jul, 2012 1 commit
-
-
Ronald S. Bultje authored
-
- 22 Jul, 2012 1 commit
-
-
Jason Garrett-Glaser authored
Simplifies pshufb masks that operate on words.
-