From: Mark H Weaver <mhw@netris.org>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH v2] Ensure that MIPS target code is compiled for the O32 ABI.
Date: Tue, 08 Sep 2015 21:37:47 -0400 [thread overview]
Message-ID: <87egi8v0d0.fsf@netris.org> (raw)
In-Reply-To: <55EF16C0.6010703@gmail.com> ("Vladimir 'φ-coder/phcoder' Serbinenko"'s message of "Tue, 8 Sep 2015 10:11:28 -0700")
"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com> writes:
> On 23.08.2015 23:50, Mark H Weaver wrote:
>> Include -mabi=32 in CFLAGS_PLATFORM and CCASFLAGS_PLATFORM to compile
>> code for the O32 ABI when targetting MIPS, since the MIPS assembly code
>> in GRUB assumes this.
> Could you be more precise where we assume this?
Well, to begin with, most of the MIPS assembly code in GRUB uses the
MIPS register names such as $tN, $sN, $aN, $vN, etc. Such code is
rejected by the assembler unless the O32 ABI is being used, which makes
sense since those names are based on the registers' roles in the O32
ABI.
In addition, I guess that any MIPS assembly code in *.S that is called
by C (or calls into C) will need to be adjusted to use the calling
conventions of the ABI in use (N32 or N64). There may be other issues
as well; I haven't researched it.
> Why not fix the assembly instead?
If someone wants to do that job, I'd be pleased, but I don't have time
to do it. I have too many other more important things to work on, and
not enough time. Too few people are working on non-Intel platforms,
leaving most of the work on both the MIPS and ARMHF ports of GNU Guix to
me. Many other important packages still need to be fixed on both MIPS
and ARMHF, whereas I have GRUB working well.
Regards,
Mark
next prev parent reply other threads:[~2015-09-09 1:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 18:35 [PATCH] Ensure that MIPS target code is compiled for the O32 ABI Mark H Weaver
2015-08-21 4:05 ` Andrei Borzenkov
2015-08-22 18:04 ` Mark H Weaver
2015-08-23 9:51 ` Andrei Borzenkov
2015-08-23 17:27 ` Mark H Weaver
2015-08-24 6:50 ` [PATCH v2] " Mark H Weaver
2015-09-08 17:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-09-09 1:37 ` Mark H Weaver [this message]
2015-09-13 6:32 ` Andrei Borzenkov
2015-10-09 21:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-10 0:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-14 4:49 ` Andrei Borzenkov
2015-10-14 12:16 ` Vladimir 'phcoder' Serbinenko
2015-10-14 17:57 ` Andrei Borzenkov
2015-08-24 7:19 ` [PATCH] " Andrei Borzenkov
2015-08-24 7:57 ` Mark H Weaver
2015-08-24 8:12 ` Andrei Borzenkov
2015-08-24 9:27 ` Andrei Borzenkov
2015-08-25 18:18 ` Mark H Weaver
2015-09-11 15:06 ` Andrei Borzenkov
2015-09-13 2:41 ` Mark H Weaver
2015-09-13 3:46 ` Mark H Weaver
2015-09-13 14:10 ` Andrei Borzenkov
2015-09-13 23:37 ` Mark H Weaver
2015-09-20 4:44 ` Andrei Borzenkov
2015-09-21 16:09 ` Mark H Weaver
2015-09-21 17:56 ` Andrei Borzenkov
2015-09-22 15:03 ` Mark H Weaver
2015-09-22 17:26 ` Andrei Borzenkov
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=87egi8v0d0.fsf@netris.org \
--to=mhw@netris.org \
--cc=grub-devel@gnu.org \
--cc=phcoder@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 NNTP newsgroup(s).