Where can I find a working winnt.h? Rubenvb's appears to be very wrong

Question

Looking thru the definitions in winnt.h from rubenvb's 4.7.2 download (c++.exe --version is rubenvb-4.7.2-release) reveals a number of routines with inline assembly that simply don't work correctly. At least they don't on my i7 processor (could these have been coded for some other processor?).

However, given the nature of how gcc is developed, it seems possible that some other implementation has done a better job with this file.

So, 2 questions:

Does anyone know where to find a better winnt.h?
Failing that, does anyone know how to contact reubanvb?

I generally use http://nuwen.net/mingw.html. Might want to wait a bit for GCC 4.8.0, though. — chris, Mar 20 '13 at 20:28
@chris: AFAIK the nuwen distribution is 32-bit only, like the main MinGW distribution. rubenvb's build, as I recall, is of MinGW-64, presumably with both 32-bit and 64-bit compiler. — Cheers and hth. - Alf, Mar 20 '13 at 20:36
@david: also re your point 2, ruben is often in the C++ Lounge chatroom here on SO. well unless i'm conflating two similar identities — Cheers and hth. - Alf, Mar 20 '13 at 20:38
Well, I just downloaded nuwen, and there is a winnt.h. However, it doesn't have any of the definitions I was looking for: bitscanforward, bittest, etc. — David Wohlferd, Mar 20 '13 at 20:45
@Alf For examples, see [http://stackoverflow.com/a/15532980/2189500](http://stackoverflow.com/a/15532980/2189500) — David Wohlferd, Mar 20 '13 at 20:48
@alf Thanks for the tip. Apparently ruben hasn't been to that chat room today, but I'll keep checking. BTW, if you want more examples, _bittest is also wrong. When the first 5 I checked were all wrong, the rest were all suspect. — David Wohlferd, Mar 20 '13 at 21:24

score 1 · Answer 1 · answered Mar 20 '13 at 23:19

1

The Windows SDK is a free download. You can get the one for Windows 8 here, or use this one to stick with targeting Windows 7. Naturally, it includes all of the headers necessary to call Windows functions, including WinNT.h.

answered Mar 20 '13 at 23:19

Cody Gray - on strike

239,200
50
490
574

I see no reason why it wouldn't be. It is the only way to develop Windows applications, so if MinGW supports developing Windows applications, it will have to support the Windows SDK. MinGW is just a C++ compiler. – Cody Gray - on strike Mar 22 '13 at 03:26
@cody I think you have missed the point. The original post made reference to "a number of routines with inline assembly." This is (part of) gcc's answer to intrinsics. The "#pragma intrinsic(_BitScanForward)" in the WSDK's winnt.h is completely ignored by gcc. The answer appears to be work with the developers at sourceforge to get these routines repaired, which is what I am doing. They are receptive, but it has been slow going. – David Wohlferd Mar 23 '13 at 04:29
Guess so. Seemed like a weird question. If there's a bug in code you're getting from a particular vendor, you should contact that vendor for support. I assumed you wanted to know "where to find a better winnt.h", and so I answered that question. – Cody Gray - on strike Mar 25 '13 at 07:00

score 1 · Accepted Answer · answered Feb 17 '15 at 04:52

1

I have worked with the Mingw-w64 team to update the asm routines in winnt.h (and other headers). To the best of my knowledge, they are all correct now.

answered Feb 17 '15 at 04:52

David Wohlferd

7,110
2
29
56

Where can I find a working winnt.h? Rubenvb's appears to be very wrong

2 Answers2