From: Christian Eggers <ceggers@gmx.de>
To: binutils@sourceware.org
Cc: Christian Eggers <ceggers@gmx.de>
Subject: [PATCH 0/7] gas: Fixes for DWARF2 debug info with OCTETS_PER_BYTE>1
Date: Sun, 10 Mar 2019 18:22:00 -0000 [thread overview]
Message-ID: <20190310182158.23705-1-ceggers@gmx.de> (raw)
I'm working on a binutils port for the SDMA controller which is inside many
of NXP's i.MX SOCs. In contrast to most other architectures, the SDMA has
16 bit per instruction address (OCTETS_PER_BYTE=2). Up to now, no architecture
with OCTETS_PER_BYTE>1 uses DWARF debug information (tic4x and tic54x use
stabs).
With OCTETS_PER_BYTE=2, the smallest addressable unit is 16 bit. This is
problematic with DWARF2 debug information, as this format always uses 8 bit
quantities. Resulting problems can be truncated sections and displaced
relocations.
These patch series fixes the generation of DWARF debug information in gas for
these architectures, which is a prerequisite for the SDMA port.
These changes should not affect existing architectures as all targets currently
using DWARF2 have 8 bit per byte.
Christian Eggers (7):
[gas] dwarf2: Fix calculation of line info offset
[gas] Allow to create symbols with octets value
[gas] dwarf2: Use octets for dwarf2 headers
[gas] dwarf2: Use octets for .debug_line prologue
[gas] dwarf2: Use octets for .debug_string offsets
[gas] dwarf2: Pad size of .debug_line section.
[gas] dwarf2: Align relocation within .debug_line section
gas/ChangeLog | 42 ++++++++++++++++++++++++++++++++++++++++++
gas/dwarf2dbg.c | 55 ++++++++++++++++++++++++++++++++++++++++++-------------
gas/symbols.c | 39 ++++++++++++++++++++++++++++++++++++++-
gas/symbols.h | 3 +++
4 files changed, 125 insertions(+), 14 deletions(-)
--
2.16.4
next reply other threads:[~2019-03-10 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 18:22 Christian Eggers [this message]
2019-03-10 18:22 ` [PATCH 6/7] [gas] dwarf2: Pad size of .debug_line section Christian Eggers
2019-03-10 18:22 ` [PATCH 7/7] [gas] dwarf2: Align relocation within " Christian Eggers
2019-03-10 18:22 ` [PATCH 3/7] [gas] dwarf2: Use octets for dwarf2 headers Christian Eggers
2019-03-10 18:22 ` [PATCH 1/7] [gas] dwarf2: Fix calculation of line info offset Christian Eggers
2019-03-10 18:22 ` [PATCH 4/7] [gas] dwarf2: Use octets for .debug_line prologue Christian Eggers
2019-03-10 18:22 ` [PATCH 5/7] [gas] dwarf2: Use octets for .debug_string offsets Christian Eggers
2019-03-10 18:27 ` [PATCH 2/7] [gas] Allow to create symbols with octets value Christian Eggers
2019-03-13 4:49 ` [PATCH 0/7] gas: Fixes for DWARF2 debug info with OCTETS_PER_BYTE>1 Alan Modra
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=20190310182158.23705-1-ceggers@gmx.de \
--to=ceggers@gmx.de \
--cc=binutils@sourceware.org \
/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).