From: Basile Starynkevitch <basile@starynkevitch.net>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ilya Verbin <iverbin@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
Uday Khedker <uday@cse.iitb.ac.in>,
hubicka@ucw.cz, rth@redhat.com, kirill.yukhin@gmail.com,
"Michael V. Zolotukhin" <michael.v.zolotukhin@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: Questions about LTO infrastructure and pragma omp target
Date: Wed, 28 Aug 2013 09:59:00 -0000 [thread overview]
Message-ID: <1377620524.1366.2.camel@glinka.lesours> (raw)
In-Reply-To: <20130823111731.GK1814@tucnak.redhat.com>
On Fri, 2013-08-23 at 13:17 +0200, Jakub Jelinek wrote:
[...]
> Then the question is what the plugin should perform with these sections,
> whether it will compile each input .gnu.target_lto section hunk separately
> (as in non-LTO mode), or with -flto also LTO them together.
[...]
Since plugins are mentioned (and I guess Jakub was talking of linker
plugins) I would add that GCC plugins might want to add (and later use)
their own arbitrary LTO data in these sections.
Cheers
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2013-08-27 16:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 13:44 Ilya Verbin
2013-08-15 15:00 ` Jakub Jelinek
2013-08-15 19:19 ` Richard Biener
2013-08-23 13:15 ` Ilya Verbin
2013-08-23 14:38 ` Jakub Jelinek
2013-08-28 9:59 ` Basile Starynkevitch [this message]
2013-08-23 15:05 ` Richard Biener
2013-08-23 15:06 ` Jakub Jelinek
2013-08-25 22:36 ` Ilya Verbin
2013-08-26 7:32 ` Jakub Jelinek
2013-09-03 14:00 ` Michael V. Zolotukhin
2013-09-03 14:19 ` Jakub Jelinek
2013-09-03 15:18 ` Michael V. Zolotukhin
2013-09-03 17:39 ` Thomas Schwinge
2013-09-03 18:30 ` Michael V. Zolotukhin
2013-09-03 18:54 ` Jakub Jelinek
2013-09-03 19:09 ` Michael V. Zolotukhin
2013-09-16 17:14 ` Ilya Verbin
2013-09-17 8:12 ` Richard Biener
2013-09-17 11:31 ` Ilya Verbin
2013-09-17 11:54 ` Jakub Jelinek
2013-09-17 11:56 ` Richard Biener
2013-09-17 12:15 ` Jakub Jelinek
2013-09-19 10:45 ` Ilya Verbin
2013-09-19 10:50 ` Jakub Jelinek
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=1377620524.1366.2.camel@glinka.lesours \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=iverbin@gmail.com \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=michael.v.zolotukhin@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=rth@redhat.com \
--cc=uday@cse.iitb.ac.in \
/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).