All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] new patch for amd64
Date: Wed, 21 Sep 2005 15:07:23 +0200	[thread overview]
Message-ID: <87mzm6o9h0.fsf@student.han.nl> (raw)
In-Reply-To: <20050920231059.9516.qmail@web35308.mail.mud.yahoo.com> (Ruslan Nikolaev's message of "Tue, 20 Sep 2005 16:10:59 -0700 (PDT)")

Ruslan Nikolaev <nruslan_devel@yahoo.com> writes:

Hi Ruslan,

> I have seen another patch for amd64 by Marco Gerards. In fact month
> ago I sent the patch that also allows compiling on x86_64.

Right, I sent in this new patch because I don't like changing LD and
CC the way you do and because there were many special cases.  I had a
look how to change this and by the time I figured out a clean way, I
already had a new patch.  Hopefully you do not feel ignored (perhaps I
should've replied to your patch with this one as an alternative or
so...), that was not my intention.  You could say I was inspired to
fix AMD64 compilation this way because of your patch.

> By the way I decided to send new patch (it's really works with amd64).
>  
> Some bugs was fixed: - it doesn't break x86 compiling now (small bug)
> - it allows you to compile grub even you haven't libc32 and other
> 32-bit libraries and OS doesn't support executing 32-bit binaries. Of
> course -m32 gcc param is always available. But as you can see you also
> can't check regparm=3 bug in this case :( That is why for x86_64
> always using regparm=2 for nested functions in this patch.

Why can't you test for the regparam=3 bug?

> !!! PLEASE NOTE THAT IT'S NOT REAL NEED TO DO SPECIAL AMD64 VERSION
> BECAUSE USER CAN CHOOSE TO LOAD 32-bit operating system under
> x86_64. Moreover you can't switch to 64-bit by bootloader because you
> need enable paging first (that is not very clear to do by bootloader).

Right.  My patch is not 64 bits either.  What I would prefer is
applying my patch because it does not change that much and doesn't
require much special cases and it is a bit better readable (that's why
I sent it in basically).

After that I could have a look at your other patch.  But I prefer to
wait until Guillem sent in his patch for 64 bits ELF support.  If that
patch is applied we could change Ruslan's patch to use that code,
but if it takes too long Ruslan's patch can be applied first.

But I am not sure if we want a 64 bits multiboot and what is involved
with changing multiboot that way.  I leave that to Okuji.

Thanks,
Marco




  parent reply	other threads:[~2005-09-21 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 23:10 [PATCH] new patch for amd64 Ruslan Nikolaev
2005-09-21 11:38 ` Yoshinori K. Okuji
2005-09-21 23:03   ` 2Yoshinori K. Okuji Ruslan Nikolaev
2005-09-21 13:07 ` Marco Gerards [this message]
2005-09-21 22:47   ` 2Marco Gerards Ruslan Nikolaev
2005-09-21 23:10     ` 2Marco Gerards (new) Ruslan Nikolaev
2005-09-22 18:16       ` Marco Gerards
2005-09-22 22:43         ` 2Marco Gerards (important info) Ruslan Nikolaev
2005-09-23 13:46           ` Marco Gerards
2005-09-24 22:17             ` 2Marco Gerards (answer) Ruslan Nikolaev

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=87mzm6o9h0.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.