On Fri, Oct 21, 2011 at 1:56 PM, Rainer Orth
wrote:
> Iain Sandoe writes:
>
>> It looks like the gnat testsuite is also broken - but HP's fix doesn't
>> recover that.
>> .. will try and take a look - but short on time today,
>
> I think I see what's going on: in gnat.log, I find
>
> Running /vol/
> Date: Fri, 21 Oct 2011 20:34:05 +0200
> From: Jan Hubicka
> I guess we could make ipa-dump/rtl-dump/tree-dump scanning to disable fat lto
> and introduce variants intended to scan late tree dumps and ipa execution
> dumps...
Ok, sounds like a plan. Are there any such
scan-tests-with-late-thi
>
> Meh... Please no, this was the kind of scatter-patches my patch
> aimed to avoid... for example, easy to miss some tests.
>
> Instead, on top of my patch, just copy the
> scan-assembler_required_options proc to a
> scan-tree-dump_required_options. ...no wait, should forcing
> fat-lto be don
> Date: Fri, 21 Oct 2011 17:44:15 +0200
> From: Jan Hubicka
> I also noticed that tests scanning output of late optimization passes are
> now getting UNRESOLVED state with slim LTO. We don't really lose coverage
> here because we test fat LTO with the other compilation, but probably easiest
> is
> If running the gnat.dg testsuite, lib/gcc-dg.exp is now calling
> check_linker_plugin_available early, which ultimately calls
> ${tool}_target_compile. For all languages but Ada,
> ${tool}_target_compile can compile .c files just fine, but
> gnat_target_compile (which uses gnatmake) cannot, so i
Iain Sandoe writes:
> It looks like the gnat testsuite is also broken - but HP's fix doesn't
> recover that.
> .. will try and take a look - but short on time today,
I think I see what's going on: in gnat.log, I find
Running /vol/gcc/src/hg/trunk/local/gcc/testsuite/gnat.dg/dg.exp ...
ERROR: tc
On 21 Oct 2011, at 10:31, Jan Hubicka wrote:
Date: Fri, 21 Oct 2011 00:19:32 +0200
From: Jan Hubicka
Yes, if we scan assembler, we likely want -fno-fat-lto-objects.
then IIUC you need to patch *all* torture tests that use
scan-assembler and scan-assembler-not. Alternatively, patch
somewher
> > Date: Fri, 21 Oct 2011 00:19:32 +0200
> > From: Jan Hubicka
> > Yes, if we scan assembler, we likely want -fno-fat-lto-objects.
>
> > > then IIUC you need to patch *all* torture tests that use
> > > scan-assembler and scan-assembler-not. Alternatively, patch
> > > somewhere else, like not pa
> Date: Fri, 21 Oct 2011 00:19:32 +0200
> From: Jan Hubicka
> Yes, if we scan assembler, we likely want -fno-fat-lto-objects.
> > then IIUC you need to patch *all* torture tests that use
> > scan-assembler and scan-assembler-not. Alternatively, patch
> > somewhere else, like not passing it if ce
> > Date: Tue, 27 Sep 2011 19:23:22 +0200
> > From: Jan Hubicka
>
> > this patch updates testsuite to cover both fat and slim LTO when linker
> > plugin
> > is used and also both linker plugin and collect2 paths. I didn't wanted to
> > slow down testing too much so I just distributes the flags
Looks like this patch broke, for cris-elf with TOT binutils:
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/torture/dg-torture.exp ...
FAIL: gcc.dg/torture/cris-asm-mof-1.c scan-assembler in-asm: .mof
FAIL: gcc.dg/torture/cris-asm-mof-1.c scan-assembler out-asm: .mof
FAIL: gcc.dg/torture
> Date: Tue, 27 Sep 2011 19:23:22 +0200
> From: Jan Hubicka
> this patch updates testsuite to cover both fat and slim LTO when linker plugin
> is used and also both linker plugin and collect2 paths. I didn't wanted to
> slow down testing too much so I just distributes the flags across existing
12 matches
Mail list logo
