Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1433208
| From | Joe Perches <joe@perches.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v1 0/2] Introduce the initify gcc plugin |
| Date | 2016-06-28 20:50 +0200 |
| Message-ID | <rP6f7-2dJ-17@gated-at.bofh.it> (permalink) |
| References | <rOZnk-6lK-27@gated-at.bofh.it> <rP4dj-11e-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 2016-06-28 at 09:35 -0700, Joe Perches wrote:
> (adding Mathias Krause who did something similar via macros in 2014)
>
> https://lkml.org/lkml/2014/6/22/149
>
> On Tue, 2016-06-28 at 13:34 +0200, Emese Revfy wrote:
> >
> > I would like to introduce the initify gcc plugin. The kernel already
> > has
> > a mechanism to free up code and data memory that is only used during
> > kernel
> > or module initialization.
> > This plugin will teach the compiler to find more such code and data
> > that
> > can be freed after initialization. It reduces memory usage.
> > The initify gcc plugin can be useful for embedded systems.
> What happens to string deduplication when one string
> is in an init function and the same string is also used
> in a non-init function in the same compilation unit?
>
> foo.c
>
> __init void initfunc(void)
> {
> pr_info("%s: I'm here\n", __func__);
> }
>
> void runtimefunc(void)
> {
> pr_info("I'm here: %s\n", __func__);
> }
>
> In what section does the string "I'm here: %s\n" get placed
> or does it get placed into multiple sections?
Sorry, Joe can't type.
That was meant to be the identical string in both functions.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 13:30 +0200
[PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy <re.emese@gmail.com> - 2016-06-28 13:40 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Joe Perches <joe@perches.com> - 2016-06-28 18:50 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy <re.emese@gmail.com> - 2016-06-28 22:40 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Joe Perches <joe@perches.com> - 2016-06-28 23:10 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy <re.emese@gmail.com> - 2016-06-29 20:50 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Joe Perches <joe@perches.com> - 2016-06-30 02:20 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy <re.emese@gmail.com> - 2016-07-01 16:00 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Rasmus Villemoes <linux@rasmusvillemoes.dk> - 2016-06-28 23:00 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute "PaX Team" <pageexec@freemail.hu> - 2016-06-28 23:50 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Rasmus Villemoes <linux@rasmusvillemoes.dk> - 2016-06-29 00:50 +0200
Re: [PATCH v1 2/2] Mark functions with the __nocapture attribute Emese Revfy <re.emese@gmail.com> - 2016-06-29 20:40 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 13:40 +0200
[PATCH v1 1/2] Add the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 13:40 +0200
Re: [PATCH v1 1/2] Add the initify gcc plugin Rasmus Villemoes <linux@rasmusvillemoes.dk> - 2016-06-28 23:10 +0200
Re: [PATCH v1 1/2] Add the initify gcc plugin Kees Cook <keescook@chromium.org> - 2016-06-29 17:00 +0200
Re: [PATCH v1 1/2] Add the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-29 21:10 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Mark Rutland <mark.rutland@arm.com> - 2016-06-28 15:00 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 18:10 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Kees Cook <keescook@chromium.org> - 2016-06-28 22:50 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Mark Rutland <mark.rutland@arm.com> - 2016-06-29 10:30 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Mark Rutland <mark.rutland@arm.com> - 2016-06-29 20:00 +0200
Re: [kernel-hardening] [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-29 20:30 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Joe Perches <joe@perches.com> - 2016-06-28 18:40 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Joe Perches <joe@perches.com> - 2016-06-28 20:50 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Rasmus Villemoes <linux@rasmusvillemoes.dk> - 2016-06-28 21:10 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 22:30 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Mathias Krause <minipli@ld-linux.so> - 2016-06-28 19:10 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Emese Revfy <re.emese@gmail.com> - 2016-06-28 22:30 +0200
Re: [PATCH v1 0/2] Introduce the initify gcc plugin Joe Perches <joe@perches.com> - 2016-06-29 00:00 +0200
Re: [kernel-hardening] Re: [PATCH v1 0/2] Introduce the initify gcc plugin Valdis.Kletnieks@vt.edu - 2016-06-29 00:10 +0200
Re: [kernel-hardening] Re: [PATCH v1 0/2] Introduce the initify gcc plugin Joe Perches <joe@perches.com> - 2016-06-29 02:00 +0200
csiph-web