From: Jim Wilson <jimw@sifive.com>
To: William Tambe <tambewilliam@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Mis-aligned debugging symbols
Date: Mon, 9 Mar 2020 14:53:16 -0700 [thread overview]
Message-ID: <CAFyWVaaAzowNy2E--fn_ptN10x--d5nf3meDPVj+EYtTak1SFQ@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mNScJjghh1dR-LdX1cD-4A1M1d03U8yptL+VGpJ7gXbRQ@mail.gmail.com>
On Sun, Mar 8, 2020 at 4:21 PM William Tambe <tambewilliam@gmail.com> wrote:
> Relocation section '.rela.debug_line' at offset 0x1fec contains 19 entries:
> Offset Info Type Sym.Value Sym. Name + Addend
> 000000f7 00000603 R_ARCH_32 00000000 .text.startup + 0
This is unaligned by design, to help reduce the size of the debug
info. Debug info isn't performance critical, so dealing with
unaligned data is not a problem here. To fix it, you would have to
use a different debug info format, but there isn't one we support as
well as dwarf2.
Jim
prev parent reply other threads:[~2020-03-09 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 14:39 William Tambe
2020-03-08 23:21 ` William Tambe
2020-03-09 21:53 ` Jim Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyWVaaAzowNy2E--fn_ptN10x--d5nf3meDPVj+EYtTak1SFQ@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tambewilliam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).