search for: kmaxregisternumb

Displaying 9 results from an estimated 9 matches for "kmaxregisternumb".

Did you mean: kmaxregisternumber
2016 Dec 23
2
3.9 regression with legacy static assert macros (bad type resolution)
....9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp In file included from src/ld/parsers/macho_relocatable_file.cpp:37: src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs 'int [1]' extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; ^ src/ld/parsers/libunwind/Registers.hpp:548:13: note: pr...
2016 Dec 27
2
3.9 regression with legacy static assert macros (bad type resolution)
...relocatable_file.cpp >>>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>>> 'int [1]' >>>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; >>>> ^ >>>...
2016 Dec 27
3
3.9 regression with legacy static assert macros (bad type resolution)
...ble_file.cpp >>>>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>>>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>>>> 'int [1]' >>>>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; >>>>> ^ &g...
2016 Dec 23
0
3.9 regression with legacy static assert macros (bad type resolution)
...valid-offsetof -c macho_relocatable_file.cpp > In file included from src/ld/parsers/macho_relocatable_file.cpp:37: > src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs > 'int [1]' > extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; > ^ > src/ld/parsers/libunwind/Registers.hp...
2016 Dec 24
2
3.9 regression with legacy static assert macros (bad type resolution)
...fsetof -c macho_relocatable_file.cpp >> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >> 'int [1]' >> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; >> ^ >> src/ld/parsers/libunwin...
2016 Dec 27
0
3.9 regression with legacy static assert macros (bad type resolution)
...c macho_relocatable_file.cpp >>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>> 'int [1]' >>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; >>> ^ >>> src/ld/pa...
2017 Jan 23
2
3.9 regression with legacy static assert macros (bad type resolution)
...t;>>>>>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>>>>>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>>>>>> 'int [1]' >>>>>>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR ) ? 1 : -1 ] __attribute__( ( unused ) );; >>>&gt...
2015 Jul 14
2
[LLVMdev] [llvm] [libunwind] r207467 misprint
...tch is: Index: DwarfInstructions.hpp =================================================================== --- DwarfInstructions.hpp (revision 242137) +++ DwarfInstructions.hpp (working copy) @@ -170,7 +170,7 @@ const int lastReg = R::lastDwarfRegNum(); assert((int)CFI_Parser<A>::kMaxRegisterNumber > lastReg && "register range too large"); - assert(lastReg <= (int)cieInfo.returnAddressRegister && + assert(lastReg >= (int)cieInfo.returnAddressRegister && "register range does not contain return address regis...
2016 Jan 19
5
LLVM libunwind stack usage
...though, in a software package that builds and runs exception-using tool at build time. The failure turned out to be a stack overflow[3] during the forced-unwind cleanup of a thread with a minimum-sized (4K) stack. LLVM libunwind has allows for 120 saved registers, common across all architectures (kMaxRegisterNumber in src/DwarfParser.hpp). In contrast the GCC unwinder has a target-dependent maximum; on x86-64 it's 18. LLVM libunwind requires 1920 bytes for register storage, vs. 288 for the GCC unwinder. Is it reasonable to change LLVM libunwind to use an approach similar to GCC's unwinder, and have...