From: Daniel Kiper <dkiper@net-space.pl>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH v2] grub-core: Build fixes for i386
Date: Thu, 27 May 2021 16:27:42 +0200 [thread overview]
Message-ID: <20210527142742.eyp6jdngxnafldfs@tomti.i.net-space.pl> (raw)
In-Reply-To: <87v9751hr0.fsf@gnu.org>
On Wed, May 26, 2021 at 08:18:11PM +0200, Jan Nieuwenhuizen wrote:
> Daniel Kiper writes:
[...]
> >> * grub-core/lib/i386/relocator64.S: Avoid x86_64 instructions on i386.
> >
> > Hmmm... What is this?
>
> The "gitlog-to-changelog" scripts needs entries like this in order to
> generate a GNU-compliant ChangeLog, see Emacs, LilyPond, Guile, Guix,
> etc. GRUB is the first GNU project that I encounter that has a
> different take on this; sorry for missing that!
Oh, I did not know about that. I have to take a look at it.
> I have changed it to
>
> --8<---------------cut here---------------start------------->8---
> This fixes cross-compiling to x86 (e.g., the Hurd) from x86-linux of
>
> grub-core/lib/i386/relocator64.S
>
> This file has six sections that only build with a 64-bit assembler,
> yet only the first two sections had support for a 32-bit assembler;
> this patch completes this for the remaining sections.
> --8<---------------cut here---------------end--------------->8---
>
> > And you should add your SOB at the end of commit message:
> >
> > Signed-off-by: Jan (janneke) Nieuwenhuizen <janneke@gnu.org>
>
> Done.
>
> And sorry; you asked that before. I failed to do so because I only ever
> encountered this use (e.g., quoting the Guix manual)
>
> When pushing a commit on behalf of somebody else, please add a
> ‘Signed-off-by’ line at the end of the commit log message—e.g., with
> ‘git am --signoff’. This improves tracking of who did what.
>
> and as I am the author, that would be redundant.
No worries...
> >> +#ifdef __x86_64__
> >> movq %rax, %rsi
> >> -
> >
> > This and...
> >
> >> +#else
> >> + /* movq %rax, %rsi */
> >> + .byte 0x48
> >> + .byte 0x89
> >> + .byte 0xc6
> >> +#endif
> >> +
> >
> > ... this change look strange. Could you fix it? Or explain in the
> > commit message you are doing a cleanup by the way...
>
> Hmm...what is it that looks strange here? Obviously the MOV %RAX..
> statement must be guarded and get a 32-bit alternative, and the empty
> line after the move instruction now moves to the end of the block?
Err... Sorry, I was imprecise. I was thinking about removal and addition
of empty lines. No entirely empty but... Anyway, I will fix it...
Daniel
prev parent reply other threads:[~2021-05-27 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 10:47 [PATCH v2] grub-core: Build fixes for i386 Jan (janneke) Nieuwenhuizen
2021-05-18 10:58 ` John Paul Adrian Glaubitz
2021-05-18 14:26 ` Daniel Kiper
2021-05-18 14:35 ` John Paul Adrian Glaubitz
2021-05-18 14:38 ` John Paul Adrian Glaubitz
2021-05-18 20:06 ` Matt Turner
2021-05-26 15:04 ` Daniel Kiper
2021-05-26 18:18 ` Jan Nieuwenhuizen
2021-05-27 14:27 ` Daniel Kiper [this message]
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=20210527142742.eyp6jdngxnafldfs@tomti.i.net-space.pl \
--to=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=janneke@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.