[Mingw-w64-public] [Patch] _bittest, _bittestandset, etc

2013-08-02 Thread dw
1) Move these functions from winnt.h to intrin-impl.h: _bittest, _bittest64 _bittestandset, _bittestandreset, _bittestandcomplement _bittestandset64, _bittestandreset64, _bittestandcomplement64 2) Update inline asm code: *a) Remove memory clobber*. *b) Remove volatile keyword.* c) Several

Re: [Mingw-w64-public] [RFC] Single filename per line in Makefiles

2013-08-02 Thread Rafaël Carré
Hi, Le 02/08/2013 20:59, Derek Buitenhuis a écrit : As it stands right now, the grouping and wrapping of filenames in MinGW-w64's Makefiles makes tracking or viewing changes in version control very very hard, and makes it non-obvious what has changed. I propose that it move to a sorted,

Re: [Mingw-w64-public] [RFC] Single filename per line in Makefiles

2013-08-02 Thread dw
Comments, flames, or questions? I like this idea too. dw -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you

[Mingw-w64-public] _lrotr and LP64

2013-08-02 Thread dw
I have some (non-asm) questions about _lrotr (long rotate right). 1. Looking at intrin.h, it uses a #ifdef __x86_64__ to change the parameters between LONG32 and LONG64. But that doesn't seem right. Shouldn't it be looking at __LP64__? Since this is mapped to msvcr*.dll in the .def

Re: [Mingw-w64-public] _lrotr and LP64

2013-08-02 Thread Kai Tietz
2013/8/3 dw limegreenso...@yahoo.com: I have some (non-asm) questions about _lrotr (long rotate right). Looking at intrin.h, it uses a #ifdef __x86_64__ to change the parameters between LONG32 and LONG64. But that doesn't seem right. Shouldn't it be looking at __LP64__? Since this is