All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	gcc@gcc.gnu.org, Mathias Krause <minipli@googlemail.com>,
	Mason <slash.tmp@free.fr>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: String literals in __init functions
Date: Thu, 02 Apr 2015 09:23:23 -0700	[thread overview]
Message-ID: <1427991803.23434.27.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1504021558350.27469@digraph.polyomino.org.uk>

On Thu, 2015-04-02 at 16:00 +0000, Joseph Myers wrote:
> On Thu, 26 Mar 2015, Joe Perches wrote:
> > > I'd have thought that a function-wide
> > > 	__attribute__((__string_section__(foo))
> > > wouldn't be a ton of work to implement.
> > 
> > Maybe not.
> > 
> > Could some future version of gcc move string constants
> > in a function to a specific section marked in a manner
> > similar to what Andrew described above?
> 
> Putting string constants in a special section is an old project idea at 
> <http://gcc.gnu.org/projects/optimize.html#putting_constants_in_special_sections>.  

That's news to me.  Thanks for the link.

> I still think support for that would make sense.

That's good to know.

Do you know of a mechanism in place to prioritize
development for these optimization projects or is
this a placeholder for unscheduled or unresourced
TODOs?


WARNING: multiple messages have this Message-ID (diff)
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: String literals in __init functions
Date: Thu, 02 Apr 2015 09:23:23 -0700	[thread overview]
Message-ID: <1427991803.23434.27.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1504021558350.27469@digraph.polyomino.org.uk>

On Thu, 2015-04-02 at 16:00 +0000, Joseph Myers wrote:
> On Thu, 26 Mar 2015, Joe Perches wrote:
> > > I'd have thought that a function-wide
> > > 	__attribute__((__string_section__(foo))
> > > wouldn't be a ton of work to implement.
> > 
> > Maybe not.
> > 
> > Could some future version of gcc move string constants
> > in a function to a specific section marked in a manner
> > similar to what Andrew described above?
> 
> Putting string constants in a special section is an old project idea at 
> <http://gcc.gnu.org/projects/optimize.html#putting_constants_in_special_sections>.  

That's news to me.  Thanks for the link.

> I still think support for that would make sense.

That's good to know.

Do you know of a mechanism in place to prioritize
development for these optimization projects or is
this a placeholder for unscheduled or unresourced
TODOs?

  reply	other threads:[~2015-04-02 16:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 17:56 String literals in __init functions Mason
2015-03-25 17:56 ` Mason
2015-03-25 18:01 ` Joe Perches
2015-03-25 18:01   ` Joe Perches
2015-03-26 12:40   ` Mason
2015-03-26 12:40     ` Mason
2015-03-26 16:13     ` Joe Perches
2015-03-26 16:13       ` Joe Perches
2015-03-26 16:37       ` Mathias Krause
2015-03-26 16:37         ` Mathias Krause
2015-03-26 17:53         ` Joe Perches
2015-03-26 17:53           ` Joe Perches
2015-03-26 20:49           ` Mathias Krause
2015-03-26 20:49             ` Mathias Krause
2015-03-26 21:40             ` Andrew Morton
2015-03-26 21:40               ` Andrew Morton
2015-03-26 21:58               ` Joe Perches
2015-03-26 21:58                 ` Joe Perches
2015-03-26 22:15                 ` Andrew Morton
2015-03-26 22:15                   ` Andrew Morton
2015-03-27  7:16                   ` Mathias Krause
2015-03-27  7:16                     ` Mathias Krause
2015-04-02 16:00                 ` Joseph Myers
2015-04-02 16:00                   ` Joseph Myers
2015-04-02 16:23                   ` Joe Perches [this message]
2015-04-02 16:23                     ` Joe Perches
2015-03-27  7:05               ` Mathias Krause
2015-03-27  7:05                 ` Mathias Krause
2015-03-27  7:32                 ` Joe Perches
2015-03-27  7:32                   ` Joe Perches

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=1427991803.23434.27.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=minipli@googlemail.com \
    --cc=slash.tmp@free.fr \
    /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.