From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752788AbbDBQXb (ORCPT ); Thu, 2 Apr 2015 12:23:31 -0400 Received: from smtprelay0207.hostedemail.com ([216.40.44.207]:33613 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752315AbbDBQX1 (ORCPT ); Thu, 2 Apr 2015 12:23:27 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 50,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::,RULES_HIT:41:355:379:541:599:960:967:973:988:989:1260:1263:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2525:2553:2560:2563:2682:2685:2687:2828:2859:2902:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3870:3871:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4321:5007:6119:6261:7903:8599:9025:9388:9855:10004:10400:10848:11026:11232:11658:11914:12043:12438:12517:12519:12740:12776:13069:13149:13230:13311:13357:14096:14097:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: basin77_751116617c92a X-Filterd-Recvd-Size: 2327 Message-ID: <1427991803.23434.27.camel@perches.com> Subject: Re: String literals in __init functions From: Joe Perches To: Joseph Myers Cc: Andrew Morton , gcc@gcc.gnu.org, Mathias Krause , Mason , Linux ARM , LKML , Ingo Molnar Date: Thu, 02 Apr 2015 09:23:23 -0700 In-Reply-To: References: <5512F6C6.1020304@free.fr> <1427306517.2717.0.camel@perches.com> <5513FE2F.3040306@free.fr> <1427386390.15849.13.camel@perches.com> <1427392393.15849.16.camel@perches.com> <20150326144058.56ef6916b00ad38030296089@linux-foundation.org> <1427407120.15849.34.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > . 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? From mboxrd@z Thu Jan 1 00:00:00 1970 From: joe@perches.com (Joe Perches) Date: Thu, 02 Apr 2015 09:23:23 -0700 Subject: String literals in __init functions In-Reply-To: References: <5512F6C6.1020304@free.fr> <1427306517.2717.0.camel@perches.com> <5513FE2F.3040306@free.fr> <1427386390.15849.13.camel@perches.com> <1427392393.15849.16.camel@perches.com> <20150326144058.56ef6916b00ad38030296089@linux-foundation.org> <1427407120.15849.34.camel@perches.com> Message-ID: <1427991803.23434.27.camel@perches.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 > . 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?