From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Felipe Balbi <balbi@ti.com>, Arnaud Lacombe <lacombar@gmail.com>,
Michal Nazarewicz <mina86@mina86.com>, Greg KH <greg@kroah.com>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: generate one module from multiple object files (was: Re: [PATCH 2/2] usb: gadget: convert all users to the new udc)
Date: Tue, 14 Jun 2011 19:16:32 +0200 [thread overview]
Message-ID: <4DF79770.8080002@linutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1106141301000.2102-100000@iolanthe.rowland.org>
Alan Stern wrote:
>> Do we support gcc --combine already ?
>
> As far as I know, the only advantage of gcc -combine is that it allows
> the optimizer to work on more than one file at a time. Would that
> really make any significant difference for these particular source
> files?
It should also remove static functions which are not used. However I
really don't know the root cause of the memory footprint.
Having every file as a separate module might be a little overkill because
you need usually ~2 guard pages per module in virtual address space. Maybe
a "library" like module.
>
> Alan Stern
>
Sebastian
next prev parent reply other threads:[~2011-06-14 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110613085534.GD3633@legolas.emea.dhcp.ti.com>
[not found] ` <Pine.LNX.4.44L0.1106131024100.1983-100000@iolanthe.rowland.org>
[not found] ` <20110613153516.GC2353@legolas.emea.dhcp.ti.com>
[not found] ` <op.vw1yw3ol3l0zgt@mnazarewicz-glaptop>
2011-06-14 7:32 ` generate one module from multiple object files (was: Re: [PATCH 2/2] usb: gadget: convert all users to the new udc) Felipe Balbi
2011-06-14 15:33 ` Arnaud Lacombe
2011-06-14 16:45 ` Felipe Balbi
2011-06-14 17:06 ` Alan Stern
2011-06-14 17:16 ` Sebastian Andrzej Siewior [this message]
2011-06-14 17:29 ` Felipe Balbi
2011-06-14 17:48 ` Arnaud Lacombe
2011-06-14 18:36 ` Felipe Balbi
2011-06-14 20:21 ` Greg KH
2011-06-14 19:27 ` Alan Stern
2011-06-14 19:41 ` Felipe Balbi
2011-06-14 20:01 ` Alan Stern
2011-06-14 20:16 ` Felipe Balbi
2011-06-14 20:24 ` Greg KH
2011-06-14 17:15 ` Arnaud Lacombe
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=4DF79770.8080002@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=greg@kroah.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=stern@rowland.harvard.edu \
/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