From: Hans-Peter Nilsson <hp@bitrange.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org
Subject: Re: Cgraph alias reorg 15/14 (New infrastructure for same body aliases)
Date: Mon, 20 Jun 2011 14:47:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1106201043180.87357@dair.pair.com> (raw)
In-Reply-To: <BANLkTikxffqgR4EPhp8t7B_5+e2W3gxO-A@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1631 bytes --]
On Mon, 20 Jun 2011, Richard Guenther wrote:
> On Sun, Jun 19, 2011 at 2:51 PM, Jan Hubicka <hubicka@ucw.cz> wrote:
> >> > On Sat, 11 Jun 2011, Jan Hubicka wrote:
> >> >
> >> > > Hi,
> >> > > this patch complettes the same body alias rework by removing the old same body
> >> > > alias code and adding new representation. Â Same body aliases are now separate
> >> > > function nodes that have IPA_REF_ALIAS reference to the node they are alias of.
> >> > >
> >> > > I am still getting one failure:
> >> > > FAIL: g++.dg/torture/pr43879-1_1.C
> >> > >
> >> > > It tests IPA PTA in presence of same body aliases. Â I honestly have no idea
> >> > > what is wrong there. Â I decided to go ahead with the patch anyway, given the
> >> > > current state of affair of aliases and IPA-PTA. Hope Richard will help me
> >> > > fixing this on Monday.
> >> >
> >> > Still there, see again PR49373. Â Anything better than a xfail in the works?
> >>
> >> Yes, we discussed the problem with Richi and the issue is that ipa-pta gets
> >> confused by inliner redirecting edge from alias to the real inline clone.
> >> The proper fix is to teach passmanager to do small ipa passes before final
> >> compilation. Â I am currently at the GCC gathering, so I plan to implement
> >> this day after tomorrow after returning.
> > But for sure we can xfail it.
> > (It was prevoiusly latent problem and richi did quicker fix but that just
> > uncovered another problems. Sorry for the delays here).
>
> If you xfail it please open a regression bugreport.
Anything wrong with the already open PR49373 where it's
mentioned?
>
> Richard.
>
> > Honza
> >
>
next prev parent reply other threads:[~2011-06-20 14:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 14:22 Jan Hubicka
2011-06-11 17:31 ` H.J. Lu
2011-06-12 9:02 ` H.J. Lu
2011-06-12 15:08 ` Jan Hubicka
2011-06-12 15:45 ` H.J. Lu
2011-06-12 15:55 ` Jan Hubicka
2011-06-12 16:33 ` H.J. Lu
2011-06-12 16:29 ` H.J. Lu
2011-06-12 17:06 ` Jan Hubicka
2011-06-12 17:46 ` H.J. Lu
2011-06-12 17:13 ` Jan Hubicka
2011-06-12 18:07 ` H.J. Lu
2011-06-12 22:11 ` Jan Hubicka
2011-06-19 12:52 ` Hans-Peter Nilsson
2011-06-19 12:55 ` Jan Hubicka
2011-06-19 14:04 ` Jan Hubicka
2011-06-20 11:23 ` Richard Guenther
2011-06-20 14:47 ` Hans-Peter Nilsson [this message]
2011-06-22 21:54 ` Hans-Peter Nilsson
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=alpine.BSF.2.00.1106201043180.87357@dair.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=richard.guenther@gmail.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).