All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	Glenn Washburn <development@efficientek.com>,
	Robin Candau <antiz@archlinux.org>
Subject: Re: [PATCH v4 3/5] efi: Drop all uses of efi_call_XX wrappers
Date: Mon, 12 Jun 2023 19:19:53 +0200	[thread overview]
Message-ID: <20230612191953.740546c8@leda.eworm.net> (raw)
In-Reply-To: <20230523153145.822782-4-ardb@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

Ard Biesheuvel <ardb@kernel.org> on Tue, 2023/05/23 17:31:
> Now that GCC can generate function calls using the correct calling
> convention for us, we can stop using the efi_call_XX () wrappers, and
> just dereference the function pointers directly.
> 
> This avoids the untyped variadic wrapper routines, which means better
> type checking for the method calls.

Building an Arch package from current git master makes the system unbootable
with just a black screen. We did biscect this and found this commit
(bb4aa6e06ee3877110a1dc0eb0d766ffac978993 in master) to be the first bad one.

As gcc is mentioned in the commit message... We are building with gcc
13.1.1-1. Any idea what is going on here?
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-06-12 17:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 15:31 [PATCH v4 0/5] efi: Implement generic EFI boot for x86 Ard Biesheuvel
2023-05-23 15:31 ` [PATCH v4 1/5] efi: Make EFI PXE protocol methods non-callable Ard Biesheuvel
2023-05-23 15:31 ` [PATCH v4 2/5] efi: Add calling convention annotation to all prototypes Ard Biesheuvel
2023-05-23 15:31 ` [PATCH v4 3/5] efi: Drop all uses of efi_call_XX wrappers Ard Biesheuvel
2023-06-12 17:19   ` Christian Hesse [this message]
2023-06-12 19:05     ` Daniel Kiper
2023-06-12 20:53       ` Robin Candau
2023-06-14 15:15         ` Daniel Kiper
2023-06-15 15:01           ` Thomas Frauendorfer
2023-06-15 15:05           ` Daniel Kiper
2023-06-15 21:36             ` Christian Hesse
2023-06-16  7:15               ` Robin Candau
2023-06-16 10:35                 ` Daniel Kiper
2023-06-16 10:48                   ` Robin Candau
2023-06-16 12:24                     ` Christian Hesse
2023-06-16 14:11                       ` Daniel Kiper
2023-05-23 15:31 ` [PATCH v4 4/5] efi: Remove x86_64 call wrappers Ard Biesheuvel
2023-05-23 15:31 ` [PATCH v4 5/5] efi: Use generic EFI loader for x86_64 and i386 Ard Biesheuvel
2023-05-23 15:34   ` Ard Biesheuvel
2024-05-16 12:24   ` [REGRESSION] " Jan Čermák
2024-05-16 13:42     ` Ard Biesheuvel
2024-06-27 10:26       ` Jan Čermák
2024-06-27 10:39         ` Mate Kukri
2024-06-28 17:28         ` Ard Biesheuvel
2024-07-03 14:25           ` Jan Čermák
2024-07-03 14:47             ` Ard Biesheuvel
2024-07-03 17:35               ` Jan Čermák
2024-07-22 10:43                 ` Jan Čermák
2023-05-24 20:21 ` [PATCH v4 0/5] efi: Implement generic EFI boot for x86 Daniel Kiper

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=20230612191953.740546c8@leda.eworm.net \
    --to=list@eworm.de \
    --cc=antiz@archlinux.org \
    --cc=ardb@kernel.org \
    --cc=daniel.kiper@oracle.com \
    --cc=development@efficientek.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 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.