Hi Mikhail,
Thanks for the comments. I haven't updated my GDB yet and I will test it
again once I have a newer version GDB.
Yuhang
On 06/06/2015 09:31 PM, Mikhail Maltsev wrote:
On 07.06.2015 0:15, steven...@gmail.com wrote:
Dear GCC developers,
I have successfully compiled & installed GC
On 07.06.2015 0:15, steven...@gmail.com wrote:
> Dear GCC developers,
>
> I have successfully compiled & installed GCC 4.9.2. Could you comment on the
> results of 'make check' (see below). Here is the relevant information:
>
You can verify it against published test results:
https://www.gnu.org/
> > On 06/06/2015 03:33 PM, Jan Hubicka wrote:
> > >Aldy,
> > >also at PPC64le LTO bootstrap (at gcc112) dies with:
> > >^
> > >0x104ae8f7 check_die
> > > ../../gcc/dwarf2out.c:5715
> >
> > Hmmm... this is in the LTO/ltrans stage? If so, that's weird. The
> > LTO path does not do the ear
> On 06/06/2015 03:33 PM, Jan Hubicka wrote:
> >Aldy,
> >also at PPC64le LTO bootstrap (at gcc112) dies with:
> >^
> >0x104ae8f7 check_die
> > ../../gcc/dwarf2out.c:5715
>
> Hmmm... this is in the LTO/ltrans stage? If so, that's weird. The
> LTO path does not do the early DIE dance. Sin
On 06/06/2015 05:47 PM, Aldy Hernandez wrote:
On 06/06/2015 03:33 PM, Jan Hubicka wrote:
Aldy,
also at PPC64le LTO bootstrap (at gcc112) dies with:
^
0x104ae8f7 check_die
../../gcc/dwarf2out.c:5715
Hmmm... this is in the LTO/ltrans stage? If so, that's weird. The LTO
path does not d
On 06/06/2015 03:33 PM, Jan Hubicka wrote:
Aldy,
also at PPC64le LTO bootstrap (at gcc112) dies with:
^
0x104ae8f7 check_die
../../gcc/dwarf2out.c:5715
Hmmm... this is in the LTO/ltrans stage? If so, that's weird. The LTO
path does not do the early DIE dance. Since check_die() is a
Dear GCC developers,
I have successfully compiled & installed GCC 4.9.2. Could you comment on the
results of 'make check' (see below). Here is the relevant information:
1. config.guess
x86_64-unknown-linux-gnu
2. gcc -v
Using built-in specs.
COLLECT_GCC=/Scr/scr-test-steven/ins
Aldy,
also at PPC64le LTO bootstrap (at gcc112) dies with:
^
0x104ae8f7 check_die
../../gcc/dwarf2out.c:5715
0x104e4e1b dwarf2out_decl
../../gcc/dwarf2out.c:21886
0x104d8a87 dwarf2out_abstract_function
../../gcc/dwarf2out.c:18457
0x104dd3e7 gen_inlined_subroutine_die
On 06/06/2015 09:20 AM, Andreas Schwab wrote:
Aldy Hernandez writes:
Does the attached fix the ia64 failure?
commit 6c40c8f011bbd09ea92749f3925db83f249baf74
Author: Aldy Hernandez
Date: Sat Jun 6 06:48:40 2015 -0400
* dwarf2out.c (gen_lexical_block_die): Initialize stmt_die.
Yes
Andreas Schwab writes:
> FAIL: gcc.dg/autopar/pr46885.c (test for excess errors)
> Excess errors:
> xgcc: error:
> /daten/aranym/gcc/gcc-20150606/gcc/testsuite/gcc.dg/autopar/pr46885.c:
> -fcompare-debug failure
As it turned out, this is a fallout from a different c
On 05/06/15 16:55, Richard Henderson wrote:
> On 06/04/2015 03:40 AM, Richard Earnshaw wrote:
>> The static chain register is pretty much private to a translation unit...
>
> That was true when the static chain was restricted to trampolines.
> Since Go has started using it for cross-translation-u
Aldy Hernandez writes:
> Does the attached fix the ia64 failure?
>
> commit 6c40c8f011bbd09ea92749f3925db83f249baf74
> Author: Aldy Hernandez
> Date: Sat Jun 6 06:48:40 2015 -0400
>
> * dwarf2out.c (gen_lexical_block_die): Initialize stmt_die.
Yes, it does.
Thanks, Andreas.
--
Andrea
On Fri, Jun 05, 2015 at 12:55:04PM +0400, Mikhail Maltsev wrote:
> 05.06.2015 13:02, Ondřej Bílka writes:
> > Also as I mentioned bugs before gcc now doesn't handle alignment well so
> > it doesn't optimize following to zero for aligned code.
> >
> > align = ((uintptr_t) x) % 16;
> >
> That is b
On 06/06/2015 05:49 AM, Andreas Schwab wrote:
Bootstrap fails on aarch64:
Comparing stages 2 and 3
warning: gcc/cc1objplus-checksum.o differs
warning: gcc/cc1obj-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
warning: gcc/cc1-checksum.o differs
Bootstrap comparison failure!
gcc/ira-c
Bootstrap fails on aarch64:
Comparing stages 2 and 3
warning: gcc/cc1objplus-checksum.o differs
warning: gcc/cc1obj-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
warning: gcc/cc1-checksum.o differs
Bootstrap comparison failure!
gcc/ira-costs.o differs
gcc/tree-sra.o differs
gcc/tree-p
:const|volatile|atomic|restrict)_type 8
I'm also seeing this:
FAIL: gcc.dg/autopar/pr46885.c (test for excess errors)
Excess errors:
xgcc: error:
/daten/aranym/gcc/gcc-20150606/gcc/testsuite/gcc.dg/autopar/pr46885.c:
-fcompare-debug failure
Andreas.
--
Andreas Schwab, sch...@linux-m68k.o
On June 5, 2015 9:06:01 PM GMT+02:00, Aldy Hernandez wrote:
>The debug-early work has been merged into mainline.
>
>There is a known Ada failure which Eric B. knows about and approved,
>and
>for which there is an appropriate FIXME note in the Ada sources:
>
>+FAIL: gnat.dg/specs/debug1.ads scan-a
17 matches
Mail list logo