From: Ard Biesheuvel <ardb@kernel.org>
To: Arvind Sankar <nivedita@alum.mit.edu>
Cc: Andrey Ignatov <rdna@fb.com>,
linux-efi <linux-efi@vger.kernel.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH 05/24] efi/libstub: Optimize for size instead of speed
Date: Fri, 5 Jun 2020 17:11:49 +0200 [thread overview]
Message-ID: <CAMj1kXHxWjijEgw9a3=t1jmCuONpBeQEBMEEcNoCyz0aOo-1xQ@mail.gmail.com> (raw)
In-Reply-To: <20200605151037.GA1011855@rani.riverdale.lan>
On Fri, 5 Jun 2020 at 17:10, Arvind Sankar <nivedita@alum.mit.edu> wrote:
>
> On Fri, Jun 05, 2020 at 04:53:59PM +0200, Ard Biesheuvel wrote:
> > I guess the logic that decides whether -maccumulate-outgoing-args is
> > enabled is somewhat opaque.
> >
> > Could we perhaps back out the -Os change for 4.8 and earlier?
>
> I just sent a patch to add the accumulate-outgoing-args option
> explicitly. That fixes 4.8.5 and doesn't seem to affect at least
> gcc-9.3.0, which presumably already enables it automatically.
>
Fair enough.
next prev parent reply other threads:[~2020-06-05 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200518190716.751506-1-nivedita@alum.mit.edu>
[not found] ` <20200518190716.751506-6-nivedita@alum.mit.edu>
2020-06-05 0:31 ` [PATCH 05/24] efi/libstub: Optimize for size instead of speed Andrey Ignatov
2020-06-05 6:33 ` Ard Biesheuvel
2020-06-05 13:14 ` Arvind Sankar
2020-06-05 13:32 ` Arvind Sankar
2020-06-05 14:53 ` Ard Biesheuvel
2020-06-05 15:10 ` Arvind Sankar
2020-06-05 15:11 ` Ard Biesheuvel [this message]
2020-06-05 15:06 ` [PATCH] efi/x86: Fix build with gcc 4 Arvind Sankar
2020-06-05 16:09 ` Andrey Ignatov
2020-06-15 9:43 ` Ard Biesheuvel
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='CAMj1kXHxWjijEgw9a3=t1jmCuONpBeQEBMEEcNoCyz0aOo-1xQ@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=rdna@fb.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).