On Fri, May 27, 2011 at 12:12 AM, Janis Johnson <jani...@codesourcery.com> wrote: > On 05/25/2011 05:15 AM, Jan Hubicka wrote: >> Am Wed 25 May 2011 11:04:06 AM CEST schrieb Richard Guenther >> <richard.guent...@gmail.com>: >> >>> On Wed, May 25, 2011 at 10:38 AM, Rainer Orth >>> <r...@cebitec.uni-bielefeld.de> wrote: >>>> Janis Johnson <jani...@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. > > This patch renames val to function_to_inline and searches for its > name in the release-ssa dump. That scan-dump has an xfail. The > original scan-dump of 'optimized' is removed. > > Richard and Jan, is this OK?
Ok. Thanks, Richard. >
