On Feb 19, 2016, at 6:53 AM, Jakub Jelinek <ja...@redhat.com> wrote:
> Looking at this, I think I have no problem with crtoffloadbegin.o being
> included in all -fopenmp/-fopenacc linked programs/shared libraries,
:-) I have a problem with just the normal init path in most executables. It
adds a ton of stuff that can be empty at the bottom. I sometimes wonder if we
boosted it to -flto, and then let lto see the size of the table, and put all
the init code under an early if (count) { do the init stuff; }, then given the
count, lto can then just remove it all, reliably.
If the openmp people want to experiment with -flto and see if they can make the
whole thing disappear that way, it might be worth considering.
But, yes, I agree, hard to want yet more included by default that just won’t go
away.
