You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/tmp/stuff/zydis/src/Generated/InstructionDefinitions.inc:3761:7: error: unknown type name 'ZydisInstructionDefinitionEVEX'; did you
mean 'ZydisInstructionDefinitionVEX'?
const ZydisInstructionDefinitionEVEX ISTR_DEFINITIONS_EVEX[] =
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ZydisInstructionDefinitionVEX
/tmp/stuff/zydis/include/Zydis/Internal/SharedData.h:815:3: note: 'ZydisInstructionDefinitionVEX' declared here
} ZydisInstructionDefinitionVEX;
^
In file included from /tmp/stuff/zydis/src/SharedData.c:43:
/tmp/stuff/zydis/src/Generated/InstructionDefinitions.inc:3763:565: warning: excess elements in struct initializer
...ZYDIS_REG_CONSTRAINTS_NONE, ZYAN_FALSE ZYDIS_NOTMIN(ZYDIS_IVECTOR_LENGTH_DEFAULT) ZYDIS_NOTMIN(ZYDIS_TUPLETYPE_T1_4X) ZYDIS_NO...
^~~~~~~~~~~~~~~~~~~~~
/tmp/stuff/zydis/src/SharedData.c:40:30: note: expanded from macro 'ZYDIS_NOTMIN'
# define ZYDIS_NOTMIN(x) , x
with the latter warning being repeated a few thousand times.
I imagine that while MSVC seems to be eating it (judging from the PR #71), this might result in corrupted tables and thus incorrect output (due to shifting etc).
The text was updated successfully, but these errors were encountered:
athre0z
added
the
C-bug
Category: This is a bug (or a fix for a bug, when applied to PRs)
label
Nov 8, 2018
MSVC does not eat this either, even though it is true in general that MSVC tends to eat a lot more than Clang does (though what actually comes out of the compiler is another matter) 😄
I did not get this error because I additionally had both ZYDIS_DISABLE_EVEX and ZYDIS_DISABLE_MVEX defined. Without those, MSVC gives essentially the same as Clang:
Building with
fails with
with the latter warning being repeated a few thousand times.
I imagine that while MSVC seems to be eating it (judging from the PR #71), this might result in corrupted tables and thus incorrect output (due to shifting etc).
The text was updated successfully, but these errors were encountered: