On Tue, 4 Feb 2014, Dominique Dhumieres wrote:
> With the petches (an a minor fix in gcc/lto/lto.c) the remaining failures
> are
>
> FAIL: gfortran.dg/debug/pr35154-dwarf2.f -gdwarf-2 scan-assembler
> (DW_AT_name: "label"|"label[^\n]*"[^\n]*DW_AT_name)
> FAIL: gfortran.dg/debug/pr35154-dwarf2.f
With the petches (an a minor fix in gcc/lto/lto.c) the remaining failures
are
FAIL: gfortran.dg/debug/pr35154-dwarf2.f -gdwarf-2 scan-assembler (DW_AT_name:
"label"|"label[^\n]*"[^\n]*DW_AT_name)
FAIL: gfortran.dg/debug/pr35154-dwarf2.f -gdwarf-2 -g3 scan-assembler
(DW_AT_name: "label"|"label[
On Tue, 4 Feb 2014, Richard Biener wrote:
> On Tue, 4 Feb 2014, Dominique Dhumieres wrote:
>
> > Richard,
> >
> > With your patch at http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00144.html
> > I get multiple ICEs when testing with
> > check-gfortran RUNTESTFLAGS="--target_board=unix'{-m32/-flto,
On Tue, 4 Feb 2014, Dominique Dhumieres wrote:
> Richard,
>
> With your patch at http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00144.html
> I get multiple ICEs when testing with
> check-gfortran RUNTESTFLAGS="--target_board=unix'{-m32/-flto,-m64/-flto}'"
>
> They are of the kind
>
> lto1: intern
Richard,
With your patch at http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00144.html
I get multiple ICEs when testing with
check-gfortran RUNTESTFLAGS="--target_board=unix'{-m32/-flto,-m64/-flto}'"
They are of the kind
lto1: internal compiler error: in mentions_vars_p, at lto/lto.c:972
Note that
On Tue, 28 Jan 2014, Jakub Jelinek wrote:
> On Tue, Jan 28, 2014 at 10:40:51AM +0100, Richard Biener wrote:
> > The patch doesn't make much sense to me. I think the problem is that
> > NAMELIST_DECL is output in a ref section (LTO_namelist_decl_ref) but
> > the output routine writes other refs (v
On Tue, Jan 28, 2014 at 10:40:51AM +0100, Richard Biener wrote:
> The patch doesn't make much sense to me. I think the problem is that
> NAMELIST_DECL is output in a ref section (LTO_namelist_decl_ref) but
> the output routine writes other refs (via stream_write_tree and
> outputting the construct
On Tue, 21 Jan 2014, Aldy Hernandez wrote:
> Hi folks.
>
> The problem here is that while streaming the DECL_NAME with stream_read_tree()
> and consequently lto_output_tree(), we trigger an ICE because we are recursing
> on the DFS walk:
>
> else
> {
> /* This is the first time we se
Aldy Hernandez wrote:
>Hi folks.
>
>The problem here is that while streaming the DECL_NAME with
>stream_read_tree() and consequently lto_output_tree(), we trigger an
>ICE
>because we are recursing on the DFS walk:
>
> else
> {
> /* This is the first time we see EXPR, write all reacha
Hi folks.
The problem here is that while streaming the DECL_NAME with
stream_read_tree() and consequently lto_output_tree(), we trigger an ICE
because we are recursing on the DFS walk:
else
{
/* This is the first time we see EXPR, write all reachable
trees to OB. */
10 matches
Mail list logo