Displaying 3 results from an estimated 3 matches for "symboltableentri".
Did you mean:
symboltableentry
2019 May 31
2
Commit 93af05e03e05d2f85b5a7e20ec3a3a543584d84f causes warning
Hello,
After commit 93af05e03e05d2f85b5a7e20ec3a3a543584d84f we have new warning but only if compiled with GCC:
In file included from /path/to/llvm/include/llvm/ExecutionEngine/Orc/ExecutionUtils.h:19:0,
from /path/to/llvm/lib/ExecutionEngine/Orc/OrcMCJITReplacement.h:23,
from /path/to/llvm/lib/ExecutionEngine/Orc/OrcMCJITReplacement.cpp:9:
2019 May 31
2
Commit 93af05e03e05d2f85b5a7e20ec3a3a543584d84f causes warning
Generally it is preferable to store bitfields using plain integer types
because MSVC has surprising behavior when packing bitfields of differing
type. MSVC, for example, will not back this into one byte:
bool a : 1;
uint8_t b : 2;
bool c : 1;
So, for LLVM or any other cross platform project, I recommend storing enums
as some integer type, using the same type for all bitfields, and adding
2013 Sep 22
1
[LLVMdev] DebugIR pass fails with an assert
Hi List,
My IR compiles fine and runs. I've tried to add DebugIR pass so
as to be able to debug and profile it (since source is an SQL query
all that I can debug and profile is IR itself).
When I tried to add it to pass manager I got the following assert:
Program received signal SIGABRT, Aborted.
0x00007ffff3fe4425 in __GI_raise (sig=<optimized out>) at