Bug 66236 - [6 Regression] FAIL: gcc.c-torture/execute/pr42691.c on alpha-linux-gnu
Summary: [6 Regression] FAIL: gcc.c-torture/execute/pr42691.c on alpha-linux-gnu
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: rtl-optimization (show other bugs)
Version: 6.0
: P3 normal
Target Milestone: 6.0
Assignee: Thomas Preud'homme
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-21 09:04 UTC by Uroš Bizjak
Modified: 2015-09-05 19:05 UTC (History)
1 user (show)

See Also:
Host:
Target: alpha-linux-gnu
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uroš Bizjak 2015-05-21 09:04:32 UTC
FAIL: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions  (internal compiler error)
FAIL: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions  (test for excess errors)
UNRESOLVED: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions  compilation failed to produce executable
FAIL: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-loops  (internal compiler error)
FAIL: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-loops  (test for excess errors)
UNRESOLVED: gcc.c-torture/execute/pr42691.c   -O3 -fomit-frame-pointer -funroll-loops  compilation failed to produce executable

Executing on host: /space/uros/gcc-build/gcc/xgcc -B/space/uros/gcc-build/gcc/ /space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c  -fno-diagnostics-show-caret -fdiagnostics-color=never    -O3 -fomit-frame-pointer -funroll-loops  -w  -lm    -o ./pr42691.exe    (timeout = 300)
spawn /space/uros/gcc-build/gcc/xgcc -B/space/uros/gcc-build/gcc/ /space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -fomit-frame-pointer -funroll-loops -w -lm -o ./pr42691.exe^M
/space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c: In function 'add':^M
/space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c:32:1: error: unrecognizable insn:^M
(insn 87 86 29 5 (set (subreg:DI (reg:V4HI 90) 0)^M
        (reg:V4HI 94)) /space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c:19 -1^M
     (expr_list:REG_DEAD (reg:V4HI 94)^M
        (nil)))^M
/space/homedirs/uros/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/execute/pr42691.c:32:1: internal compiler error: in extract_insn, at recog.c:2341^M
0x1207809c7 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)^M
        ../../gcc-svn/trunk/gcc/rtl-error.c:110^M
0x120780a17 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)^M
        ../../gcc-svn/trunk/gcc/rtl-error.c:118^M
0x120747bcf extract_insn(rtx_insn*)^M
        ../../gcc-svn/trunk/gcc/recog.c:2341^M
0x120b99d5f union_match_dups^M
        ../../gcc-svn/trunk/gcc/web.c:118^M
0x120b99d5f execute^M
        ../../gcc-svn/trunk/gcc/web.c:395^M
Comment 1 Uroš Bizjak 2015-05-21 09:25:56 UTC
Caused by r223113.

This problem can be triggered by a crosscompiler to alpha-linux-gnu.
Comment 2 Thomas Preud'homme 2015-05-21 10:08:32 UTC
Hi Uroš, I tried with a n alpha-linux-gnu GCC cross-compiler built from revision 223280 but couldn't reproduce this. I configured it with just --prefix and --target=alpha-linux-gnu and tried compiling the testcase with -S -O3 -fomit-frame-pointer -funroll-loops.

Is there something else I missed?
Comment 3 Thomas Preud'homme 2015-05-21 11:08:20 UTC
Alternatively, you can try the patch proposed at [1] and see if it fixes the issue you're facing since it seems to be the same one.

[1] https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01901.html

Best regards.
Comment 4 Uroš Bizjak 2015-05-21 11:28:40 UTC
(In reply to Thomas Preud'homme from comment #3)
> Alternatively, you can try the patch proposed at [1] and see if it fixes the
> issue you're facing since it seems to be the same one.
> 
> [1] https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01901.html

Thomas,

yes the referred patch also fixes this issue.

Thanks!
Comment 5 Bernd Edlinger 2015-09-05 19:02:10 UTC
(In reply to Uroš Bizjak from comment #4)
> (In reply to Thomas Preud'homme from comment #3)
> > Alternatively, you can try the patch proposed at [1] and see if it fixes the
> > issue you're facing since it seems to be the same one.
> > 
> > [1] https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01901.html
> 
> Thomas,
> 
> yes the referred patch also fixes this issue.
> 
> Thanks!

that was committed already.  Thus this one should be fixed too?
Comment 6 Uroš Bizjak 2015-09-05 19:05:42 UTC
(In reply to Bernd Edlinger from comment #5)

> that was committed already.  Thus this one should be fixed too?

Yes, this was fixed.