Displaying 20 results from an estimated 200 matches similar to: "[LLVMdev] Request to push patches for PR17982 to release 3.4 branch"
2013 Dec 05
2
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
Final review is done. Feel free to merge :)
Thanks for the wait.
-eric
On Tue, Dec 3, 2013 at 1:27 PM, Eric Christopher <echristo at gmail.com> wrote:
> I request that we hold off until the final review is done.
>
> -eric
>
> On Tue, Dec 3, 2013 at 12:06 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>> This set of patches add support for debug info
2013 Dec 03
0
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
I request that we hold off until the final review is done.
-eric
On Tue, Dec 3, 2013 at 12:06 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
> This set of patches add support for debug info metadata version and debug
> info metadata will be dropped if a loaded bit code has no version or an
> outdated version.
>
> 195494: Debug Info: add a constant for debug info
2013 Dec 09
0
[LLVMdev] Request to push patches for PR17982 to release 3.4 branch
These don’t apply cleanly to the 3.4 branch. Could you add them in yourself?
-bw
On Dec 5, 2013, at 2:08 PM, Eric Christopher <echristo at gmail.com> wrote:
> Final review is done. Feel free to merge :)
>
> Thanks for the wait.
>
> -eric
>
> On Tue, Dec 3, 2013 at 1:27 PM, Eric Christopher <echristo at gmail.com> wrote:
>> I request that we hold off
2013 Nov 22
2
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com>wrote:
>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Thu, Nov 21, 2013 at
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Thu, Nov 21, 2013 at
2013 Nov 21
2
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com>wrote:
>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Thu, Nov 21, 2013 at
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Fri, Nov 22, 2013 at 9:08 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com>
>> wrote:
>>>
>>>
>>>
>>>
>>> On Thu,
2013 Nov 22
2
[LLVMdev] bit code file incompatibility due to debug info changes
On Fri, Nov 22, 2013 at 9:54 AM, Eric Christopher <echristo at gmail.com>wrote:
> On Fri, Nov 22, 2013 at 9:08 AM, David Blaikie <dblaikie at gmail.com> wrote:
> >
> >
> >
> > On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com>
> wrote:
> >>
> >>
> >>
> >>
> >> On Thu, Nov 21, 2013 at
2013 Nov 22
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Fri, Nov 22, 2013 at 10:14 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Fri, Nov 22, 2013 at 9:54 AM, Eric Christopher <echristo at gmail.com>
> wrote:
>>
>> On Fri, Nov 22, 2013 at 9:08 AM, David Blaikie <dblaikie at gmail.com> wrote:
>> >
>> >
>> >
>> > On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren
2010 May 20
2
[LLVMdev] Remove debug info from the byte code?
Hiya,
Is there any easy way to remove the debug info from the LLVM byte code
once I have collected all the debug info I needed? It is because the
debug info seems to slow down the program significantly. I may be able
to go through each basic block and delete the debug info in my pass.
But, is there any elegant way to do it?
Cheers,
Zheng
2010 May 20
0
[LLVMdev] Remove debug info from the byte code?
Hi Zheng,
> Is there any easy way to remove the debug info from the LLVM byte code
> once I have collected all the debug info I needed? It is because the
> debug info seems to slow down the program significantly. I may be able
> to go through each basic block and delete the debug info in my pass.
> But, is there any elegant way to do it?
the opt tool has an option called
2012 Apr 05
3
[LLVMdev] Implementing minimal debug info (-g1?) for Clang
Hi!
Currently Clang "-g" flag emits full debug info, which is fine for
debugging, but increases the binary size significantly.
It may be useful to produce less debug info, that is still enough for
collecting nice stack traces with file names and line numbers,
but would introduce less overhead. Cary Coutant made a patch which does
this for GCC (it didn't hit trunk yet) -
reduces
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
2013 Nov 18
3
[LLVMdev] bit code file incompatibility due to debug info changes
I just filed this as pr17982, but I'd like to call attention to it, since it seems like something we should try to fix in the 3.4 release.
Here's the description from the PR:
Sometime over the last year, and I'm fairly certain it has been since we released 3.3, the debug info metadata format has changed in incompatible ways. If you try to use an older bit code file with the current
2013 Nov 21
3
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 10:57 AM, David Blaikie <dblaikie at gmail.com>wrote:
>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 10:38 AM, Manman Ren <manman.ren at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Nov 19, 2013 at
2013 Nov 21
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Thu, Nov 21, 2013 at 10:57 AM, David Blaikie <dblaikie at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Thu, Nov 21, 2013 at
2013 Nov 21
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 10:57 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 10:38 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Nov 19, 2013 at 8:47 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Nov 19, 2013 at
2013 Nov 21
3
[LLVMdev] bit code file incompatibility due to debug info changes
On Thu, Nov 21, 2013 at 10:38 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Tue, Nov 19, 2013 at 8:47 PM, Manman Ren <manman.ren at gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Nov 19, 2013 at 5:26 PM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Mon, Nov 18, 2013 at
2012 Apr 09
0
[LLVMdev] Implementing minimal debug info (-g1?) for Clang
On Apr 5, 2012, at 10:24 AM, Alexey Samsonov <samsonov at google.com> wrote:
> Hi!
>
> Currently Clang "-g" flag emits full debug info, which is fine for debugging, but increases the binary size significantly.
> It may be useful to produce less debug info, that is still enough for collecting nice stack traces with file names and line numbers,
> but would introduce
2013 Nov 19
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Nov 19, 2013, at 1:31 PM, Eric Christopher <echristo at gmail.com> wrote:
>> Two questions:
>>
>> 1) Can we reopen the bugzilla PR that I filed and use that to cover the
>> additional of a version number and code to ignore the debug info when the
>> version number does not match? Eric has already closed it twice, so I'm
>> asking this time