Displaying 20 results from an estimated 42 matches for "stripsymbols".
2013 Nov 22
2
[LLVMdev] bit code file incompatibility due to debug info changes
...pass right after
>>>>>>>>> loading the bit code, to remove debug intrinsics and debug tags on
>>>>>>>>> instructions.
>>>>>>>>>
>>>>>>>>
>>>>>>>> We have an existing pass StripSymbols that can strip debug info in
>>>>>>>> the module.
>>>>>>>> So it is just a matter of adding that pass after bit code loader if
>>>>>>>> the debug info version number does not match.
>>>>>>>>
>>>...
2013 Nov 21
2
[LLVMdev] bit code file incompatibility due to debug info changes
...ers. One possibility is to run a module pass right after
>>>>>>> loading the bit code, to remove debug intrinsics and debug tags on
>>>>>>> instructions.
>>>>>>>
>>>>>>
>>>>>> We have an existing pass StripSymbols that can strip debug info in
>>>>>> the module.
>>>>>> So it is just a matter of adding that pass after bit code loader if
>>>>>> the debug info version number does not match.
>>>>>>
>>>>>
>>>>> Ca...
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
...is to run a module pass right after
>>>>>>>> loading the bit code, to remove debug intrinsics and debug tags on
>>>>>>>> instructions.
>>>>>>>>
>>>>>>>
>>>>>>> We have an existing pass StripSymbols that can strip debug info in
>>>>>>> the module.
>>>>>>> So it is just a matter of adding that pass after bit code loader if
>>>>>>> the debug info version number does not match.
>>>>>>>
>>>>>>
>...
2015 Aug 21
2
Canonical representation for empty lists in debug info metadata
While checking for serialization/deserialization without using pointee
types, I've come across a few test cases that crash at head, without my
debugging assertions for accessing pointee types.
One of them is test/Transforms/StripSymbols/2010-06-30-StripDebug.ll
Its retainedTypes metadata points to a metadata array of a single null
element.
This crashes the dyn_cast (because it's not a dyn_cast_or_null)
Verifier.cpp:3785
Do you have a preferred/canonical representation intended in this case - an
extant, but zero-length list,...
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
...>>>>>>>>>> loading the bit code, to remove debug intrinsics and debug tags on
>>>>>>>>>> instructions.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We have an existing pass StripSymbols that can strip debug info in
>>>>>>>>> the module.
>>>>>>>>> So it is just a matter of adding that pass after bit code loader if
>>>>>>>>> the debug info version number does not match.
>>>>>>>>...
2013 Nov 21
3
[LLVMdev] bit code file incompatibility due to debug info changes
...e loader but it seems a violation
>>>>> of layers. One possibility is to run a module pass right after loading the
>>>>> bit code, to remove debug intrinsics and debug tags on instructions.
>>>>>
>>>>
>>>> We have an existing pass StripSymbols that can strip debug info in the
>>>> module.
>>>> So it is just a matter of adding that pass after bit code loader if the
>>>> debug info version number does not match.
>>>>
>>>
>>> Can I assume no objection to the approach? :)
>...
2013 Nov 21
0
[LLVMdev] bit code file incompatibility due to debug info changes
...s a violation
>>>>>> of layers. One possibility is to run a module pass right after loading the
>>>>>> bit code, to remove debug intrinsics and debug tags on instructions.
>>>>>>
>>>>>
>>>>> We have an existing pass StripSymbols that can strip debug info in the
>>>>> module.
>>>>> So it is just a matter of adding that pass after bit code loader if
>>>>> the debug info version number does not match.
>>>>>
>>>>
>>>> Can I assume no objection...
2013 Nov 22
2
[LLVMdev] bit code file incompatibility due to debug info changes
...>>>> loading the bit code, to remove debug intrinsics and debug tags
> on
> >>>>>>>>>> instructions.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> We have an existing pass StripSymbols that can strip debug info
> in
> >>>>>>>>> the module.
> >>>>>>>>> So it is just a matter of adding that pass after bit code loader
> if
> >>>>>>>>> the debug info version number does not match.
> >...
2013 Dec 03
2
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
...g Info: add a constant for debug info version number.
195495: Debug Info: add a "Debug Info Version" module flag to output the
current debug info version number.
195504: Debug Info: update testing cases to specify the debug info version
number.
195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to
DebugInfo.cpp.
195535: Debug Info: update testing cases to specify the debug info version
number.
196143: Expand comments for Debug Info Version.
196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h
to Metadata.h.
196145: Debug Info: Move the constant for Debug Info Vers...
2013 Nov 21
0
[LLVMdev] bit code file incompatibility due to debug info changes
...this in the bit code loader but it seems a violation
>>>> of layers. One possibility is to run a module pass right after loading the
>>>> bit code, to remove debug intrinsics and debug tags on instructions.
>>>>
>>>
>>> We have an existing pass StripSymbols that can strip debug info in the
>>> module.
>>> So it is just a matter of adding that pass after bit code loader if the
>>> debug info version number does not match.
>>>
>>
>> Can I assume no objection to the approach? :)
>> Bill, are you okay...
2013 Nov 21
3
[LLVMdev] bit code file incompatibility due to debug info changes
...gt; We could do this in the bit code loader but it seems a violation of
>>> layers. One possibility is to run a module pass right after loading the bit
>>> code, to remove debug intrinsics and debug tags on instructions.
>>>
>>
>> We have an existing pass StripSymbols that can strip debug info in the
>> module.
>> So it is just a matter of adding that pass after bit code loader if the
>> debug info version number does not match.
>>
>
> Can I assume no objection to the approach? :)
> Bill, are you okay with adding another mode to...
2013 Dec 05
2
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
...number.
>> 195495: Debug Info: add a "Debug Info Version" module flag to output the
>> current debug info version number.
>> 195504: Debug Info: update testing cases to specify the debug info version
>> number.
>> 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to
>> DebugInfo.cpp.
>> 195535: Debug Info: update testing cases to specify the debug info version
>> number.
>> 196143: Expand comments for Debug Info Version.
>> 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to
>> Metadata.h.
>...
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
...sics and debug tags
>> >>>>>>>>>> on
>> >>>>>>>>>> instructions.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> We have an existing pass StripSymbols that can strip debug info
>> >>>>>>>>> in
>> >>>>>>>>> the module.
>> >>>>>>>>> So it is just a matter of adding that pass after bit code loader
>> >>>>>>>>> if
>&g...
2013 Dec 03
0
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
...r debug info version number.
> 195495: Debug Info: add a "Debug Info Version" module flag to output the
> current debug info version number.
> 195504: Debug Info: update testing cases to specify the debug info version
> number.
> 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to
> DebugInfo.cpp.
> 195535: Debug Info: update testing cases to specify the debug info version
> number.
> 196143: Expand comments for Debug Info Version.
> 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to
> Metadata.h.
> 196145: Debug Info: Mo...
2013 Dec 09
0
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
...; 195495: Debug Info: add a "Debug Info Version" module flag to output the
>>> current debug info version number.
>>> 195504: Debug Info: update testing cases to specify the debug info version
>>> number.
>>> 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to
>>> DebugInfo.cpp.
>>> 195535: Debug Info: update testing cases to specify the debug info version
>>> number.
>>> 196143: Expand comments for Debug Info Version.
>>> 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to
>...
2009 Feb 03
0
[LLVMdev] Proposal: Debug information improvement - keep the line number with optimizations
Hi Patel,
Here is second part of my reply.
> 2. Proposed Work Plan
> > This section defines a proposed work plan to accomplish the
> > requirements that we desires. The work plan is broken into several
> > distinct phases that follow a logical progression of modifications
> > to the LLVM software.
> >
> > 2.1 Phase 1: Establish the testing
2013 Nov 20
2
[LLVMdev] bit code file incompatibility due to debug info changes
...t; when to drop the debug info MDNodes?
> We could do this in the bit code loader but it seems a violation of
> layers. One possibility is to run a module pass right after loading the bit
> code, to remove debug intrinsics and debug tags on instructions.
>
We have an existing pass StripSymbols that can strip debug info in the
module.
So it is just a matter of adding that pass after bit code loader if the
debug info version number does not match.
Manman
> 4> how to report warning?
> Is errs() << "WARNING: " good enough? BTW this is how we emit warning
>...
2017 Mar 12
2
What does it mean by a "DICompileUnit missing from llvm.dgs.cu" ? | Where is the error ?
..."-polly-dump-before"?
Can you pass the dumped IR through 'opt' without seeing an error? In
this case, the
IR that enters Polly is still correct, but Polly might mis-transform it.
An alternative fix would be to extract the debug-info stripping
functionality in lib/Transforms/IPO/StripSymbols.cpp into its own
function and call this on our Kernel-IR. It is unlikely that we want to
debug GPU kernels, so we can just remove debug information for now.
Best,
Tobias
>
> - Dave
>
>
> >
> > Thank You,
> > Sanjay
> > _______________________________________...
2018 Jan 12
2
StripDeadDebugInfo for static inline functions.
Hi Paul,
Thanks for your response.
Let me actually post more details visualizing my case. Assuming that can
help.
so the IR before the opt tool is running is:
; Function Attrs: nounwind
define i16 @main() #0 !dbg !13 {
entry:
%retval = alloca i16, align 1
...
}
; Function Attrs: inlinehint nounwind
define internal void @delay(i16 %d) #4 !dbg !69 {
entry:
%d.addr = alloca i16,
2013 Nov 21
0
[LLVMdev] bit code file incompatibility due to debug info changes
...info MDNodes?
>> We could do this in the bit code loader but it seems a violation of
>> layers. One possibility is to run a module pass right after loading the bit
>> code, to remove debug intrinsics and debug tags on instructions.
>>
>
> We have an existing pass StripSymbols that can strip debug info in the
> module.
> So it is just a matter of adding that pass after bit code loader if the
> debug info version number does not match.
>
Can I assume no objection to the approach? :)
Bill, are you okay with adding another mode to module flags? i.e. emits a
war...