From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH v2] Ensure that MIPS target code is compiled for the O32 ABI.
Date: Wed, 14 Oct 2015 20:57:55 +0300 [thread overview]
Message-ID: <561E97A3.5060102@gmail.com> (raw)
In-Reply-To: <CAEaD8JMoAC4r6WYxCoz5EEQBgR7D1SLfVFB+8=rQKt66s7S=Hg@mail.gmail.com>
14.10.2015 15:16, Vladimir 'phcoder' Serbinenko пишет:
> Le 14 oct. 2015 6:50 AM, "Andrei Borzenkov" <arvidjaar@gmail.com> a écrit :
>>
>> 10.10.2015 03:28, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>>
>>> On 09.10.2015 23:14, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>>
>>>> On 13.09.2015 08:32, Andrei Borzenkov wrote:
>>>>>
>>>>> 08.09.2015 20:11, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>>>>>>
>>>>>> 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? Why not fix the
> assembly
>>>>>> instead?
>>>>>
>>>>>
>>>>> If I understand it correctly, this is not only about assembly - ABIs
>>>>> differ in sizes of types as well,
>>>>
>>>> Only in obscure types long double and uint128_t. We use neither.
>>>
>>> Correction: I was comparing o32 to n32. We still need to ensure that
>>> either o32 or n32 is used. It's easier to just ensure that o32 is used,
>>> so that we have less variability in the code but can be relaxed later if
>>> need be.
>>
>>
>> I see that you committed my suggested patch but I find comments (and
> commit message) a bit misleading. While grub main code is fixed, the
> configure asm test not, and that was the first thing that failed.
>>
> Can you please elaborate on how am test fails? The only failure I have seen
> was due to usage of $t4 and I replaced it with $t0
Sorry, missed patch for asm-tests/mips.S
>>>> f) int grub_setjmp (grub_jmp_buf env) // grub_jmp_buf is an array, so
>>>> pointer
>>>> g) int grub_longjmp (grub_jmp_buf env, int val)
>>>
>>> Correction: setjmp/longjmp are not adapted to n32 but we don't use them
>>> anyway. Probably it's time to delete the dead code after double checking
>>> that extras don't use it either.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
next prev parent reply other threads:[~2015-10-15 22:04 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
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 [this message]
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=561E97A3.5060102@gmail.com \
--to=arvidjaar@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).