Hello dw,
I try my best to read through your long e-mail ... (I want to get the
kudos ;) ). And thank you for reviewing this inline-assembler. This
is much appreachiated. Most of this stuff is implemented in a way it
works for me, but code didn't had a general review.
At the beginning I want
Hello Corinna,
patch is ok. Please apply
Thanks for the work,
Kai
--
Own the Future-Intelreg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash,
Why are those intrinsics even implemented using inline assembler
instead of GCC's own built-in functions like __builtin_ffs() for
_BitScanForward(), __sync_add_and_fetch() for _InterlockedAdd(), etc.?
--
VZ
--
Own the
2013/3/28 Corinna Vinschen vinsc...@redhat.com:
On Mar 28 11:47, Kai Tietz wrote:
Hello Corinna,
patch is ok. Please apply
Thanks. What about the script? Check in (where) or not?
Corinna
The script could go into the tools' folder in the experimental tree.
Kai
Hello Kai. Thank you for the detailed response. It takes someone brave
to wade into a post that long.
To respond to your points:
I disagree here.
The cite from http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html
Well, it's good to know that we are (literally) on the same page about
where
Actually, I looked at doing just that. And while this is possible, my
experience suggest that gcc's built-ins don't do *quite* the same
thing. For example, __builtin_ffs() returns 0 if no bits are set, or
the 1-based bit position if a bit is set. BitScanForward return a BOOL
to indicate no
I'm toying with lzo on Windows 7 32-bit (mingwbuilds 4.8.0 and rubenvb 4.7.2)
and want to create a solid patch for configure.ac, but my autoconf fu hovers
around the nano-fu level. While the failure is not a mingw-w64 bug, you guys
likely have a better battle-tested solution than my
2013/3/29 Jon jon.for...@gmail.com
I'm toying with lzo on Windows 7 32-bit (mingwbuilds 4.8.0 and rubenvb
4.7.2) and want to create a solid patch for configure.ac, but my autoconf
fu hovers around the nano-fu level. While the failure is not a mingw-w64
bug, you guys likely have a better
