From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH, RFC, RFT] ARM relocation fixes
Date: Tue, 03 Dec 2013 06:37:33 +0100 [thread overview]
Message-ID: <529D6E1D.3010806@gmail.com> (raw)
In-Reply-To: <20131202204622.GO24997@rocoto.smurfnet.nu>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
On 02.12.2013 21:46, Leif Lindholm wrote:
> On Mon, Dec 02, 2013 at 09:04:47PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>>> My default ARMv7 UEFI build fails to grub-install with
>>>>> /work/local/grub/uefi/sbin/grub-install: error: bl/b.w targettting ARM.
>>>>
>>>> This is a problem because of asm functions which are always ARM and gcc
>>>> uses bl to jump to them from thumb that an't be satisified. I wonder if
>>>> it's better to add veneers to mkimage or to add explicit thumb interwork
>>>> to all asm functions like I did in my other patch.
>>>
>>> Ah. When linking with a standalone linker, it rewrites BL to BLX where
>>> this is required for state change
>>
>> Doesn't this require Thumb2 ?
>
> No, BLX immediate has been supported since ARMv5T.
> (Yes, that is effectively a 32-bit encoding in what is a 16-bit
> instruction set - but so is the basic BL.)
>
I've looked through encoding of those instructions and see how much it's
a mess. b* and b*x don't have similar set of options which makes
validating them a difficult error-prone task. So I think, I'll just add
veneers to mkimage, just like we do on ia64 (either by making a
pc-relative variant of veneers or adding fixup for them)
> /
> Leif
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-12-03 5:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 6:06 [PATCH, RFC, RFT] ARM relocation fixes Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 10:53 ` Leif Lindholm
2013-12-02 10:58 ` Leif Lindholm
2013-12-02 10:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 11:28 ` Leif Lindholm
2013-12-02 11:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 11:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 13:30 ` Leif Lindholm
2013-12-02 14:14 ` Leif Lindholm
2013-12-02 14:33 ` Leif Lindholm
2013-12-02 17:32 ` Leif Lindholm
2013-12-02 17:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 17:38 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 17:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 19:40 ` Leif Lindholm
2013-12-02 20:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 20:46 ` Leif Lindholm
2013-12-03 5:37 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-03 8:14 ` Leif Lindholm
2013-12-03 8:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 8:47 ` Leif Lindholm
2013-12-03 9:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 11:16 ` Leif Lindholm
2013-12-03 12:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 8:09 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-03 11:23 ` Leif Lindholm
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=529D6E1D.3010806@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 NNTP newsgroup(s).