From: Jan Hubicka <hubicka@ucw.cz>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, CHKP] Fix ipa-comdats for instrumentation thunks
Date: Mon, 06 Apr 2015 18:41:00 -0000 [thread overview]
Message-ID: <20150406184126.GA8444@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <CAMbmDYY2h1H5G5B4FW8kkLEopvHr--CfyFDgU8oXVRvDEUJKhw@mail.gmail.com>
> 2015-04-03 20:12 GMT+03:00 Jan Hubicka <hubicka@ucw.cz>:
> >>
> >> Currently ipa_comdats doesn't set comdat groups for thunks. At the
> >
> > I see, that is a bug. It is supposed to keep thunks in the same section
> > as their target (thunks doesn't really work across sections on some target,
> > like PPC, because there is no way to produce a tailcall)
> > Does the following fix the problem?
>
> I believe this should help. Will try it.
If it passes testing, the patch is preapproved.
Thanks!
Honza
>
> Thanks,
> Ilya
>
> > Index: ipa-comdats.c
> > ===================================================================
> > --- ipa-comdats.c (revision 221857)
> > +++ ipa-comdats.c (working copy)
> > @@ -377,12 +377,12 @@
> > fprintf (dump_file, "To group: %s\n", IDENTIFIER_POINTER (group));
> > }
> > if (is_a <cgraph_node *> (symbol))
> > - dyn_cast <cgraph_node *>(symbol)->call_for_symbol_and_aliases
> > + dyn_cast <cgraph_node *>(symbol)->call_for_symbol_thunks_and_aliases
> > (set_comdat_group_1,
> > *comdat_head_map.get (group),
> > true);
> > else
> > - symbol->call_for_symbol_and_aliases
> > + symbol->call_for_symbol_thunks_and_aliases
> > (set_comdat_group,
> > *comdat_head_map.get (group),
> > true);
> >
next prev parent reply other threads:[~2015-04-06 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 15:45 Ilya Enkovich
2015-04-02 17:04 ` Jan Hubicka
2015-04-03 8:03 ` Ilya Enkovich
2015-04-03 17:13 ` Jan Hubicka
2015-04-06 16:16 ` Ilya Enkovich
2015-04-06 18:41 ` Jan Hubicka [this message]
2015-04-07 14:08 ` Ilya Enkovich
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=20150406184126.GA8444@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).