Displaying 11 results from an estimated 11 matches for "cfi_parser".
2016 Dec 23
2
3.9 regression with legacy static assert macros (bad type resolution)
...---
~ $ clang++-mp-3.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/Reg...
2016 Dec 27
2
3.9 regression with legacy static assert macros (bad type resolution)
...id-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 ) );;
>>>...
2011 May 30
2
[LLVMdev] Crash in libunwind
...observe it with LLVM 2.9, but not with LLVM 2.8, everything else being the same. The crash occurs when dynamically generated code calls code that tries to unwind the stack.
Here is what the stack trace looks like on MacOSX 10.6 :
0 libSystem.B.dylib 0x00007fff87297bdb libunwind::CFI_Parser<libunwind::LocalAddressSpace>::parseCIE(libunwind::LocalAddressSpace&, unsigned long long, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::CIE_Info*) + 75
1 libSystem.B.dylib 0x00007fff87298795 libunwind::CFI_Parser<libunwind::LocalAddressSpace>::decodeF...
2016 Dec 27
3
3.9 regression with legacy static assert macros (bad type resolution)
...tof -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 ) );;
>...
2016 Dec 23
0
3.9 regression with legacy static assert macros (bad type resolution)
...lang++-mp-3.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/par...
2016 Dec 24
2
3.9 regression with legacy static assert macros (bad type resolution)
...p-3.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 ) );;
>> ^
>&...
2016 Dec 27
0
3.9 regression with legacy static assert macros (bad type resolution)
...no-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 ) );;
>>>...
2017 Jan 23
2
3.9 regression with legacy static assert macros (bad type resolution)
...locatable_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__( ( u...
2011 May 30
0
[LLVMdev] Crash in libunwind
...2.9, but not with LLVM 2.8, everything else being the same. The crash occurs when dynamically generated code calls code that tries to unwind the stack.
>
> Here is what the stack trace looks like on MacOSX 10.6 :
>
> 0 libSystem.B.dylib 0x00007fff87297bdb libunwind::CFI_Parser<libunwind::LocalAddressSpace>::parseCIE(libunwind::LocalAddressSpace&, unsigned long long, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::CIE_Info*) + 75
> 1 libSystem.B.dylib 0x00007fff87298795 libunwind::CFI_Parser<libunwind::LocalAddressSpace>::de...
2015 Jul 14
2
[LLVMdev] [llvm] [libunwind] r207467 misprint
...ter in assert.
So patch 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 c...
2020 Jan 27
2
Stack Usage is more in the libunwind library .
...All,
We recently migrated to llvm 9 from gcc -7 and found that the stack
usage is more like 5K in the below function
getInfoFromDwarfSection() @ line : 1484
<https://github.com/llvm-mirror/libunwind/blob/master/src/UnwindCursor.hpp#L1484>
With our analysis and found that "typename CFI_Parser<A>::PrologInfo
prolog" local data is taking up almost 4K space.
So we thinking to refactor the code by pushing the "prolog" to a global
scope.
Any comments on our approach will be appreciated
Thank you
~Umesh
-------------- next part --------------
An HTML attachment was scrub...