Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] Fwd: Deadline for DWARF Version 5 comments -- March 31, 2014"
2017 Dec 04
5
[RFC] - Deduplication of debug information in linkers (LLD).
Hi all !
We have an issue with LLD, it is "relocation R_X86_64_32 out of range" (PR31109)
which occurs during resolving relocations in debug sections. It looks happens
because .debug_info section can be too large sometimes and 32x relocation is not enough
to represent the value. One of possible solutions looks to be to deduplicate information
to reduce .debug_info size.
The rest of
2019 Sep 11
4
Remove obsolete debug info while garbage collecting
Debuginfo and linker folks, we (AccessSoftek) would like to suggest a proposal for removing obsolete debug info. If you find it useful we will be happy to work on improving it. Thank you for any opinions and suggestions.
Alexey.
Currently when the linker does garbage collection a lot of abandoned debug info is left behind (see Appendix A for documentation). Besides inflated debug info size,
2017 Dec 04
5
[RFC] - Deduplication of debug information in linkers (LLD).
Thanks for providing the experimental data! It clearly shows the value of type sections in DWARF.
Regarding why type sections are off by default, aside from the issue of consumers needing to understand them, there is a size penalty to type sections that becomes more evident in smaller projects (meaning, fewer compilation units). The size penalty can be balanced against the amount of
2009 Jun 28
0
[LLVMdev] The document fault in llvm doc. And a comiling error
most html document need to add
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
int <head> section of html
such as
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
other staff
</head>
this is the correct style.
.\llvm\docs\SourceLevelDebugging.html
Chris Lattner sabre at nondot.org
2020 Jul 27
2
Switch to ld.bfd tombstone behavior by default
> I still think that we do bfd locs with a decent option to change for at least the current release and sources and then, once we're a little more certain we have everything that might want to parse dwarf (say by working with dwarf-discuss), we can change the default.
Given what’s been found, I think Eric/Dave are correct, use bfd behavior by default with an option to do the new thing.
2015 Nov 23
6
Building for older versions
Hi --
I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS. I'm running into
problems with versioning of memcpy in Glibc. Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.
My online search suggests to add an asm() with a .symver
option to select memcpy from
2017 Dec 04
2
[RFC] - Deduplication of debug information in linkers (LLD)
At least one proprietary linker put a lot of effort into deduplicating and
rewriting debug information. This took up the majority of the link time
despite serious engineering time on performance optimisation. For example,
some sections were written from scratch by the linker because that proved
faster than parsing the input. Teaching LLD to dedup DWARF should be
expected to dramatically slow it
2020 Jul 29
2
Switch to ld.bfd tombstone behavior by default
Created https://reviews.llvm.org/D84825 to be used for release/11.x
I haven't seen a strong argument for changing other .debug_* but in
any case I don't want to continue debating on this topic.
* .debug_ranges & .debug_loc: -2 (lld<11: 0+addend)
* .debug_*: 0 (lld<11: 0+addend, lld HEAD: -1)
On Mon, Jul 27, 2020 at 12:47 PM David Blaikie <dblaikie at gmail.com> wrote:
2012 Jul 10
3
System crash -- no clue why
Hi --
My CentOS 5.8 server crashed, leaving no clue why. The
last entry in /var/log/messages is a dhcpd notice around
4:00am, followed by the restart message when I rebooted.
The only clue that I have is that the fan was running full
speed when I restarted it. The fan slowed to normal speed.
Any ideas what I can do to find out the cause?
--
Michael Eager eager at eagercon.com
1960 Park
2011 Mar 08
12
Server hangs on CentOS 5.5
Hi --
I'm running a server which is usually stable, but every
once in a while it hangs. The server is used as a file
store using NFS and to run VMware machines.
I don't see anything in /var/log/messages or elsewhere
to indicate any problem or offer any clue why the system
was hung.
Any suggestions where I might look for a clue?
--
Michael Eager eager at eagercon.com
1960 Park Blvd.,
2019 Dec 06
2
[DWARF5][SplitDwarf] question on using fsplit-dwarf-inlining option
Hi DebugInfo folks,
I have a question on using fsplit-dwarf-inlining option:
"-fsplit-dwarf-inlining, -fno-split-dwarf-inlining
Provide minimal debug info in the object/executable to facilitate online
symbolication/stack traces in the absence of .dwo/.dwp files when using
Split DWARF"
i.e. it puts some debug info into compilation unit from First
partition(with Skeleton unit).
At
2020 Jul 30
3
Switch to ld.bfd tombstone behavior by default
On 2020-07-29, Eric Christopher wrote:
>I think the arguments are largely compatibility for software that's already
>deployed and can't easily upgrade, and wanting to ensure a larger time
>frame for migration with a fallback if things go wrong. A bridge basically
>from what we had to where we'd like to be.
>
>I think we also need to make the change in mainline lld as
2020 Mar 10
2
DWARF .debug_aranges data objects and address spaces
Hello
I've been looking at a debuginfo issue on an out-of-tree target which uses
DWARF aranges.
The problem is that aranges are generated for both data and code objects, and
the debugger gets confused when program addresses overlap data addresses. The
target is a Harvard Architecture CPU, so the appearance of overlapping address
ranges is not in itself a bug as they reside in different
2018 Jan 17
6
Adding DWARF5 accelerator table support to llvm
Hello all,
In <https://reviews.llvm.org/D41986#977215> it was brought up that
there are at least two parties interested in having DWARF5 accelerator
tables implemented, so I'm writing this email to see if there's anyone
else interested in this topic, and to try to synchronize our efforts.
Our interest for this stems from a desire to make dwarf parsing fast
on non-apple targets
2015 Nov 23
1
Building for older versions
On 11/23/2015 09:10 AM, Nicolas Thierry-Mieg wrote:
> On 11/23/2015 06:00 PM, Michael Eager wrote:
>> On 11/23/2015 08:06 AM, Nicolas Thierry-Mieg wrote:
>>> On 11/23/2015 04:33 PM, Michael Eager wrote:
>>>> Hi --
>>>>
>>>> I'm trying to build an application on CentOS 7 which
>>>> can run on older versions of CentOS. I'm
2019 Dec 24
3
Problems installing CentOS 8
I'm having a problem installing CentOS 8 from a USB drive. When the
installer boots from the USB, it displays the language selection screen.
After I select English and continue, the installer freezes. The USB
drive flashes a couple times over the next minute or so, the stops. The
mouse moves the cursor, but the installer is unresponsive to either
selecting QUIT or HELP.
I've
2020 Aug 05
2
Switch to ld.bfd tombstone behavior by default
Can we please just revert back to what we had before until the
discussion about the desired behaviour and how to get there reaches a
conclusion?
In particular, I would like to merge that revert to the 11.x branch.
At this point in the release process, I'm not keen on taking any patch
that changes the behavior to something that hasn't been well tested
from sitting in trunk for a while.
On
2020 Aug 05
3
Switch to ld.bfd tombstone behavior by default
As I mentioned in the thread (to many people who don't have time to
read the discussions), pushing https://reviews.llvm.org/D84825
restores the original behavior.
The same effect as one would get by reverting all related patches. If
someone gives me an approval, I'll push it immediately. I already get
verbal LGTM from Peter.
> With respect I think the "request for changes"
2019 Dec 02
3
addition of vendor dwarf operator extension.
Hello all,
There is one enhancement request open for dwarfv5, http://dwarfstd.org/ShowIssue.php?issue=191107.1
The request is for addition of dwarf expression operator to swap the top of the dwarf stack, the response seems positive but it may take some time till v6.
I like to add that operator as vendor extension but I am not sure how to go about it for llvm/lldb. Currently I am using it as
2010 Dec 09
0
[LLVMdev] question on generating dwarf metadata
On Mon, Dec 6, 2010 at 12:50 PM, Bagel <bagel99 at gmail.com> wrote:
> On 12/06/2010 12:03 PM, Devang Patel wrote:
> > As I understand, you are not interested in 'how to use DIFactory'. Do you
> want
> > to know what are the fields of metadata to encode debug info for a local
> variable ?
> > That'd be
> >
> > !7 = metadata !{
> >