[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[schwab@linux-m68k.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |5.0

[Bug tree-optimization/63734] New: [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[schwab@linux-m68k.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

            Bug ID: 63734
           Summary: [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c
                    -O2  (internal compiler error)
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: schwab@linux-m68k.org
                CC: glisse at gcc dot gnu.org
            Target: ia64-*-*

$ gcc/xgcc -Bgcc/ ../gcc/testsuite/gcc.dg/torture/vshuf-v8qi.c -O2 -lm -o
./vshuf-v8qi.exe
../gcc/testsuite/gcc.dg/torture/vshuf-v8qi.c: In function ‘test_3’:
../gcc/testsuite/gcc.dg/torture/vshuf-v8qi.c:10:0: internal compiler error: in
gen_reg_rtx, at emit-rtl.c:1030
 #include "vshuf-main.inc"
 ^
0x400000000064179f gen_reg_rtx(machine_mode)
        ../../gcc/emit-rtl.c:1030
0x4000000001503b4f expand_vec_perm_interleave_2
        ../../gcc/config/ia64/ia64.c:11540
0x400000000150485f ia64_expand_vec_perm_const_1
        ../../gcc/config/ia64/ia64.c:11620
0x4000000001504b6f ia64_vectorize_vec_perm_const_ok
        ../../gcc/config/ia64/ia64.c:11749
0x4000000000b83b2f can_vec_perm_p(machine_mode, bool, unsigned char const*)
        ../../gcc/optabs.c:6580
0x4000000000724baf fold_ternary_loc(unsigned int, tree_code, tree_node*,
tree_node*, tree_node*, tree_node*)
        ../../gcc/fold-const.c:14271
0x4000000000837baf gimple_fold_stmt_to_constant_1(gimple_statement_base*,
tree_node* (*)(tree_node*))
        ../../gcc/gimple-fold.c:4582
0x40000000011e7b3f try_to_simplify
        ../../gcc/tree-ssa-sccvn.c:3387
0x40000000011e7b3f visit_use
        ../../gcc/tree-ssa-sccvn.c:3464
0x40000000011eb19f extract_and_process_scc_for_name
        ../../gcc/tree-ssa-sccvn.c:3911
0x40000000011eb19f DFS
        ../../gcc/tree-ssa-sccvn.c:3963
0x40000000011ee18f cond_dom_walker::before_dom_children(basic_block_def*)
        ../../gcc/tree-ssa-sccvn.c:4242
0x4000000001690e4f dom_walker::walk(basic_block_def*)
        ../../gcc/domwalk.c:188
0x40000000011ec6af run_scc_vn(vn_lookup_kind)
        ../../gcc/tree-ssa-sccvn.c:4334
0x4000000001173a6f execute
        ../../gcc/tree-ssa-pre.c:4885

Broken by r217033.

2014-11-03  Marc Glisse  <marc.glisse@inria.fr>

    PR tree-optimization/63666
    * fold-const.c: Include "optabs.h".
    (fold_ternary_loc) <VEC_PERM_EXPR>: Avoid canonicalizing a
    can_vec_perm_p permutation to one that is not.
>From gcc-bugs-return-465701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Nov 04 11:00:49 2014
Return-Path: <gcc-bugs-return-465701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31434 invoked by alias); 4 Nov 2014 11:00:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31397 invoked by uid 48); 4 Nov 2014 11:00:44 -0000
From: "dyle at dyle dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63614] With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV
Date: Tue, 04 Nov 2014 11:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dyle at dyle dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-63614-4-3DDaPptytm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63614-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00173.txt.bz2
Content-length: 927

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc614

Oliver Maurhart <dyle at dyle dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Oliver Maurhart <dyle at dyle dot org> ---
Thank you for the hint.

Using valgrind gave me the warning of "switching stacks?", which let me
increase my stack-size, which wasn't enough, which gave me the final clue, that
my last changes exploded the stack with way too great local variables arrays.

Re reconfigured my code to create dynamic arrays as local vars like

    std::unqiue_ptr<uint64_t[]> d(new uint64_t[REAL_LARGE_NUMBER_HERE]);

instead of just

    uint64_t d[REAL_LARGE_NUMBER_HERE];

Now my stack feels fine again.

Thx.

Solved - invalid.

[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[glisse at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
My first impression is that this is a target issue, we should be able to call
TARGET_VECTORIZE_VEC_PERM_CONST_OK from gimple. Either the target should avoid
calling gen_reg_rtx when we are only calling the predicate, or it should do
what is necessary to make gen_reg_rtx not fail.

I am surprised because I would expect it to be reproducible (with a different
testcase) without my patch, since vector lowering calls can_vec_perm_p.

Does anyone have a different interpretation of what is happening?

[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P4

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
IA64 ... unmaintained. yadayada.

[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|5.0                         |5.2

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 5.1 has been released.

[Bug tree-optimization/63734] [5.0 regression] FAIL: gcc.dg/torture/vshuf-v8qi.c -O2 (internal compiler error)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63734

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|5.2                         |5.3

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 5.2 is being released, adjusting target milestone to 5.3.