[IsBadWritePtr]

Hi recently i have updated my Intel compiler to 19 and i have experienced 2 nasty bugs

The first one I don't have code to show but there was 2-3 functions that had NTAPI  and FORCEINLINE and where not included in the object file, after restarting my computer got fixed ?

The second one is pure example why companies shouldn't rush projects

Code:

// static          CHAR szBasedNamesObject[] = "\\??\\BasedNamedObject\\"; // static VOLATILE CHAR szBasedNamesObject[] = "\\??\\BasedNamedObject\\"; static CONST    CHAR szBasedNamesObject[] = "\\??\\BasedNamedObject\\"; BOOL CheckInstance(VOID) {    printf("You workin fam ? %s", szBasedNamesObject);    return TRUE; }

If the variable szBasedNamesObject is not constant is stored as (PΣá6¿Ö!║æedObject\... I did tried C11 and C99 and removing /GF (read-only string pooling optimization) nothing works. If you ware going to buy 19 i recommend to use or stay on 18. Great compile overall

[Drako]

Huh, that's odd. Another crappy Intel product issue. I heard good things about this compiler about its speed and performance. I'm currently using Cygwin for my compiler. Your code is C++ right?

[IsBadWritePtr]

C, i figured out the problem, the problem is with /Qipo and xilink, and Intel compiler is actually the best in the market, they have so many options and the inline assembly for x64 is really good and the object files and has full support for MSVC, If you want high control over optimization and the code output is the best tool, I used to use GCC but It killed me the inline assembly and the documentation and the maximum optimization back them was too buggy to be used

[darkninja1980]

C, i figured out the problem, the problem is with /Qipo and xilink, and Intel compiler is actually the best in the market, they have so many options and the inline assembly for x64 is really good and the object files and has full support for MSVC, If you want high control over optimization and the code output is the best tool, I used to use GCC but It killed me the inline assembly and the documentation and the maximum optimization back them was too buggy to be used

What was the problem with xilink?

[IsBadWritePtr]

I don't know, i think is just unitializied read or a pointer was corrupted, this bug destroyed 2 3 project... I told Intel about the bug it should be fixed on the next update