From: Mike Stump <mikestump@comcast.net>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ilya Verbin <iverbin@gmail.com>,
bschmidt@redhat.com, gcc-patches@gcc.gnu.org,
kirill.yukhin@gmail.com, thomas@codesourcery.com,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH][RFC][Offloading] Fix PR68463
Date: Fri, 19 Feb 2016 17:58:00 -0000 [thread overview]
Message-ID: <1AB0A86D-23EA-4046-8C1F-7E04DC66A2AE@comcast.net> (raw)
In-Reply-To: <20160219145308.GM3017@tucnak.redhat.com>
On Feb 19, 2016, at 6:53 AM, Jakub Jelinek <jakub@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.
next prev parent reply other threads:[~2016-02-19 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:26 Ilya Verbin
2016-01-15 8:15 ` Richard Biener
2016-01-18 20:34 ` Ilya Verbin
2016-01-19 8:57 ` Richard Biener
2016-01-19 9:36 ` Jakub Jelinek
2016-01-19 13:32 ` Ilya Verbin
2016-02-10 17:20 ` Ilya Verbin
2016-02-19 14:53 ` Jakub Jelinek
2016-02-19 17:58 ` Mike Stump [this message]
2016-02-20 10:55 ` Ilya Verbin
2016-02-22 10:59 ` Jakub Jelinek
2016-02-22 15:13 ` Thomas Schwinge
2016-02-22 18:08 ` Ilya Verbin
2016-02-23 7:37 ` Tom de Vries
2016-02-24 16:13 ` Thomas Schwinge
2016-02-24 16:30 ` Ilya Verbin
2016-02-24 19:30 ` Ilya Verbin
2016-02-24 19:35 ` Jakub Jelinek
2016-05-10 15:41 ` [PATCH] Apply fix for PR68463 to RS6000 James Norris
2016-05-10 15:49 ` David Edelsohn
2016-05-10 15:59 ` Ilya Verbin
2016-05-11 14:13 ` Thomas Schwinge
2016-05-11 14:18 ` James Norris
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=1AB0A86D-23EA-4046-8C1F-7E04DC66A2AE@comcast.net \
--to=mikestump@comcast.net \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iverbin@gmail.com \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=rguenther@suse.de \
--cc=thomas@codesourcery.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).