From: Jan Beulich <jbeulich@suse.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org, "Wei Liu" <wl@xen.org>,
"Jason Andryuk" <jandryuk@gmail.com>
Subject: Re: [PATCH 0/2] Fixups for fcf-protection
Date: Wed, 13 May 2020 11:01:15 +0200 [thread overview]
Message-ID: <89ad0ca5-c575-80da-bde3-e87d2df1c4ba@suse.com> (raw)
In-Reply-To: <27da328a-189a-607c-0f97-705405380c1b@canonical.com>
On 13.05.2020 07:41, Stefan Bader wrote:
> On 12.05.20 20:47, Andrew Cooper wrote:
>> On 12/05/2020 08:17, Stefan Bader wrote:
>>> Not sure it was already hit but that additional .note section breaks the build
>>> of the emulator as generated headers become gigantic:
>>>
>>> https://git.launchpad.net/ubuntu/+source/xen/tree/debian/patches/1001-strip-note-gnu-property.patch?h=ubuntu/focal
>>
>> 4.6G of notes?!? That is surely a toolchain bug.
>
> No, sorry if that was unclear. The .notes themselves are just about some Kb or
> so per object file. Problem is that each object file gets converted into a hex
> array header file. And this does multiply the resulting header file sizes.
> So the .h files generated are 4.6G in size. And there were a couple of those,
> all included into one .c file. Which ended in the compiler running out of memory
> on a 32GB system.
But as per the link above it's still 3Mb notes per object,
which still seems insane.
Jan
prev parent reply other threads:[~2020-05-13 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 3:39 [PATCH 0/2] Fixups for fcf-protection Jason Andryuk
2020-05-12 3:39 ` [PATCH 1/2] xen/x86: Disable fcf-protection when necessary to build Jason Andryuk
2020-05-12 3:39 ` [PATCH 2/2] x86/boot: Drop .note.gnu.properties in build32.lds Jason Andryuk
2020-05-12 15:32 ` Jan Beulich
2020-05-12 15:58 ` Andrew Cooper
2020-05-12 16:11 ` Jan Beulich
2020-05-12 16:13 ` Andrew Cooper
2020-05-12 16:17 ` Jason Andryuk
2020-05-12 19:10 ` Andrew Cooper
2020-05-12 7:17 ` [PATCH 0/2] Fixups for fcf-protection Stefan Bader
2020-05-12 18:47 ` Andrew Cooper
2020-05-13 5:41 ` Stefan Bader
2020-05-13 9:01 ` Jan Beulich [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=89ad0ca5-c575-80da-bde3-e87d2df1c4ba@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jandryuk@gmail.com \
--cc=roger.pau@citrix.com \
--cc=stefan.bader@canonical.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.