On Thu, May 07, 2015 at 07:31:33AM -0600, Jeff Law wrote:
> If you could cobble together a little test (ppc specific is fine with
> me) it'd be appreciated.
>
> With that, approved for the trunk.
I did one for *-*-linux*. Tested on powerpc64-linux and x86_64-linux.
Committed.
Segher
2015-05
tch:
- - -
Make mergeable read-only sections per-function, if requested.
Currently GCC does not put mergeable read-only data in a per-function
section, so the --gc-sections linker option does not do much for such
data. Fix that.
Bootstrapped and tested on powerpc64-linux; no regressions.
Is this okay
On 05/07/2015 02:15 AM, Marek Polacek wrote:
On Wed, May 06, 2015 at 03:59:33PM -0700, Segher Boessenkool wrote:
Currently GCC does not put mergeable read-only data in a per-function
section, so the -gc-sections linker option does not do much for such
data. Fix that.
Dunno if it is a good ide
s. Fixed.
Thanks for the review. New patch:
- - -
Make mergeable read-only sections per-function, if requested.
Currently GCC does not put mergeable read-only data in a per-function
section, so the --gc-sections linker option does not do much for such
data. Fix that.
Bootstrapped and tested
On Wed, May 06, 2015 at 03:59:33PM -0700, Segher Boessenkool wrote:
> Currently GCC does not put mergeable read-only data in a per-function
> section, so the -gc-sections linker option does not do much for such
> data. Fix that.
Dunno if it is a good idea, but...
> diff --git a/gcc/varasm.c b/gc
Currently GCC does not put mergeable read-only data in a per-function
section, so the -gc-sections linker option does not do much for such
data. Fix that.
Bootstrapped and tested on powerpc64-linux; no regressions.
Is this okay for trunk?
Segher
2015-05-06 Segher Boessenkool
PR m
