Web lists-archives.com

[Mingw-users] best value for guarding MinGW patches

I have been doing test builds of the gcc 7 release candidates and 
have found and fixed a problem in the c++ run-time library that
crashes the build.

I want to submit a patch to the upstream gcc that will 

A: isolate the MinGW-specific patch from other build environments


B: not require any modifications/improvements  by the upstream
gcc crew, as that would almost certainly mean that it would not
get into the upcoming release.

What is the best #ifdef or #if defined  value that I can use for this?

In some of the patches used for the current MinGW gcc 5.3.0,
I see

#if defined(_WIN32) 

Should I go with this or is there a better one?

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
MinGW-users mailing list

This list observes the Etiquette found at 
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at:
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe