-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual Studio 2017 support #34
Comments
Could you provide compiler output (output tab instead of the errors tab) so I can see the error code or at least translate what they say? |
Commit b37d4de builds without error and seems to work with 'printf', 'wprintf', 'puts', and '_putws'. With 'cout' it gives an error for wide chars (chars work fine): I'm fine without the optimizations and can work around 'cout' so for now that commit works as a work-around. Thanks for sharing the project. |
Seems to be just a prompt error, compiled through |
@Paavs-Git So I looked into it and the only mitigation I could do in my code is add an |
@JustasMasiulis I assume you mean to VS 2019, correct? I'm using Win 10 LTSB (2016) which is not supported by VS 2019, unfortunately. |
Yup :(
I'd suggest to just use that commit then, because functionality wise nothing changed. The problem is that VS 2017 can't handle intrinsics inside of pack expansion so I'd need to copy the parts where intrinsics are used into their own separate function. |
the lastest one almost perfectg but it has
i do use the commit for vs2017 above but its kinda exposed qmemcpy(SubStr, "garbagetext", 12);
*(_DWORD *)&SubStr[12] = -392595922;
v7.m128i_i64[0] = 0xdeedbeef;
v7.m128i_i64[1] = 0xdeedbeef;
*(__m128i *)SubStr = _mm_xor_si128(*(__m128i *)SubStr, v7);
if ( !strstr(v0, SubStr) ) the latest one kinda pog v6.m128i_i64[0] = 0xdeedbeef;
v6.m128i_i64[1] = 0xdeedbeef;
v13.m128i_i64[0] = 0xdeedbeef;
v13.m128i_i64[1] = 0xdeedbeef;
v6 = _mm_xor_si128(v6, v13);
if ( sub_100037B0(v0, &v6) ) sadly only works on vs2019 |
As shown in the figure
The text was updated successfully, but these errors were encountered: