From: "Vincent Rivière" <vincent.riviere@freesbee.fr>
To: gcc@gcc.gnu.org
Subject: Relocations to odd addresses in .eh_frame section
Date: Mon, 4 Sep 2023 14:36:48 +0200 [thread overview]
Message-ID: <87701805-40eb-8412-9650-47bbcd665d78@freesbee.fr> (raw)
Hi,
By looking at the sections generated by m68k-elf-g++, I noticed there
was relocations to odd addresses in the .eh_frame section. Is this
expected? Is there a way to avoid that, maybe by adding some padding?
Actually, I would like to upgrade the experimental m68k-atari-mintelf
toolchain from SJ/LJ exceptions to DWARF2. But the operating system
can't handle relocations to odd addresses. So I wonder if there is a
solution.
Cheers,
--
Vincent Rivière
next reply other threads:[~2023-09-04 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:36 Vincent Rivière [this message]
2023-09-04 15:06 ` Andreas Schwab
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=87701805-40eb-8412-9650-47bbcd665d78@freesbee.fr \
--to=vincent.riviere@freesbee.fr \
--cc=gcc@gcc.gnu.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).