From: Jan Hubicka <jh@suse.de>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Janis Johnson <janisjo@codesourcery.com>,
gcc-patches@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: [testsuite] remove XFAIL for all but ia64 for g++.dg/tree-ssa/pr43411.C
Date: Wed, 25 May 2011 13:38:00 -0000 [thread overview]
Message-ID: <20110525141511.xasy3kaxww8g8g00@imap.suse.de> (raw)
In-Reply-To: <BANLkTinYM2_twbujmoJUBHt4mO+bO9CvLA@mail.gmail.com>
Am Wed 25 May 2011 11:04:06 AM CEST schrieb Richard Guenther
<richard.guenther@gmail.com>:
> On Wed, May 25, 2011 at 10:38 AM, Rainer Orth
> <ro@cebitec.uni-bielefeld.de> wrote:
>> Janis Johnson <janisjo@codesourcery.com> writes:
>>
>>> Archived test results for 4.7.0 for most processors with C++ results have:
>>>
>>> XPASS: g++.dg/tree-ssa/pr43411.C scan-tree-dump-not optimized
>>> "OBJ_TYPE_REF"
>>>
>>> The only failures I could find were for ia64-linux and ia64-hpux. This
>>> patch changes the xfail so it only applies to ia64-*-*. OK for trunk?
>>
>> Richard rejected a similar patch:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2011-05/msg00054.html
>>
>> Perhaps Jan can suggest the correct approach?
>
> We should verify that the call to val is inlined in all functions.
> Maybe rename it to something larger and scan the optimized
> dump so that name doesn't appear.
Indeed, this seems to be safest approach I can think of.
If function is supposed to be optimized out completely by early
passes, we should just search release_ssa. It is not the case here
and dumping IPA info for inlining all instance would be bit tricky.
Honza
next prev parent reply other threads:[~2011-05-25 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 20:40 Janis Johnson
2011-05-25 6:20 ` Mike Stump
2011-05-25 9:58 ` Rainer Orth
2011-05-25 10:29 ` Richard Guenther
2011-05-25 13:38 ` Jan Hubicka [this message]
2011-05-27 3:57 ` Janis Johnson
2011-05-27 9:54 ` Richard Guenther
2011-05-25 19:24 ` Mike Stump
2011-05-26 10:43 ` Richard Guenther
2011-05-26 16:13 ` Mike Stump
2011-05-26 17:25 ` Richard Guenther
2011-05-27 3:55 ` Mike Stump
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=20110525141511.xasy3kaxww8g8g00@imap.suse.de \
--to=jh@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@codesourcery.com \
--cc=jh@suse.cz \
--cc=richard.guenther@gmail.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).