This improves our support for clang under Windows. - #817
Conversation
|
@jkeiser This PR uses @pps83's trick of forcing the inclusion of specific headers (which one is not supposed to do) and it therefore avoids the messiness of having to do things like Compared to @pps83's PR (and the current master), this PR carefully distinguishes between clang-under-windows and regular visual studio... |
…portforclangwindows
|
AH. Of all things, it is the new getopt thing that hits me. |
|
@lemire is it? It looks like it has some kind of issue when it tries to set up the checkperf reference branch repository. I have a PR coming that will mitigate this ... we shouldn't be building the whole tree when we fuzz anyway. |
|
LOL I see, you are plagued with both problems. |
|
@jkeiser Please review. |
jkeiser
left a comment
There was a problem hiding this comment.
This all looks very reasonable. Just the one question, whether you can still build with cmake -DSIMDJSON_IMPLEMENTATION_HASWELL=OFF (i.e. whether westmere can compile even if we don't do all the header gymnastics in AVX2).
…portforclangwindows
…lemire/simdjson into dlemire/improvingsupportforclangwindows
…simdjson/simdjson into dlemire/improvingsupportforclangwindows
|
I am waiting for this to complete its run. I think that this is quite cool. |
|
This is indeed super exciting! It lets us build Windows executables with all the optimization we normally have :) |
Fixes #763