Displaying 20 results from an estimated 42 matches for "stripsymbol".
Did you mean:
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.
>>>>>>
>>>>>
>>>>> C...
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.
>>>>>>>
>>>>>>
&g...
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.
> &g...
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 Ver...
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.
&g...
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
>&...
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: M...
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
...ons:
> > 1. Just remove the variable declaration information and
> > clean up the dead debug information.
> >
> > 2. Remove all the debug information and clean up
> >
> > 3.2.1 Work Plan
> > 1. Take a reference to transform pass StripSymbol.cpp
> > 2. Based on the StripSymbol.cpp, add an option to it to just
> > remove debug information, like "-rm-debug"
>
>
> That's what -strip-debug is doing.
>
>
>> > 3. Add an option to just remove the variable declaration...
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.
...bprogram(name: "delay", scope: !14, file: !14, line: 9,
type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags:
DIFlagPrototyped, isOptimized: true, variables: !72)
...
!73 = !DILocalVariable(name: "i", scope: !69, file: !14, line: 9, type: !11)
...
I checked the StripSymbol.cpp file and there is no difference between
version I am using (from clang 3.8) and current (6.0.0) version.
As you can see the !12 node does not contain reference to !69 after
optimizations which I think is incorrect. I assume that !69 has not been
removed because there are two nodes (!68 and !73...
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
wa...