public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94449] [10 Regression] FAIL: gcc.c-torture/execute/pr92904.c gcc.dg/torture/pr48731.c
Date: Wed, 01 Apr 2020 22:38:38 +0000	[thread overview]
Message-ID: <bug-94449-4-iUIJ7iacYV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94449-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
/export/gnu/import/git/gcc-test-master-intel64/bld/gcc/xgcc
-B/export/gnu/import/git/gcc-test-master-intel64/bld/gcc/
/export/gnu/import/git/gcc-test-master-intel64/src-master/gcc/testsuite/gcc.c-torture/execute/pr92904.c
-mx32 -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions -w -lm -o ./pr92904.exe
/export/gnu/import/git/gcc-test-master-intel64/src-master/gcc/testsuite/gcc.c-torture/execute/pr92904.c:
In function 'f1':
/export/gnu/import/git/gcc-test-master-intel64/src-master/gcc/testsuite/gcc.c-torture/execute/pr92904.c:23:1:
error: missing definition
for SSA_NAME: _98 in statement:
_69 = _98;
during GIMPLE pass: vect
/export/gnu/import/git/gcc-test-master-intel64/src-master/gcc/testsuite/gcc.c-torture/execute/pr92904.c:23:1:
internal compiler error: verify_ssa failed
0xfa5802 verify_ssa(bool, bool)
        ../../src-master/gcc/tree-ssa.c:1208
0xcbec85 execute_function_todo
        ../../src-master/gcc/passes.c:1992
0xcbf9cc do_per_function
        ../../src-master/gcc/passes.c:1640
0xcbf9cc execute_todo
        ../../src-master/gcc/passes.c:2039
Please submit a full bug report, 
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report. 
See <https://gcc.gnu.org/bugs/> for instructions.
compiler exited with status 1

  parent reply	other threads:[~2020-04-01 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 17:14 [Bug middle-end/94449] New: " hjl.tools at gmail dot com
2020-04-01 22:26 ` [Bug middle-end/94449] " hjl.tools at gmail dot com
2020-04-01 22:29 ` hjl.tools at gmail dot com
2020-04-01 22:38 ` hjl.tools at gmail dot com [this message]
2020-04-01 22:48 ` hjl.tools at gmail dot com
2020-04-01 22:50 ` hjl.tools at gmail dot com
2020-04-01 22:52 ` hjl.tools at gmail dot com
2020-04-02  0:01 ` linkw at gcc dot gnu.org
2020-04-02  1:03 ` linkw at gcc dot gnu.org
2020-04-02  1:06 ` hjl.tools at gmail dot com
2020-04-02  2:28 ` linkw at gcc dot gnu.org
2020-04-02  2:38 ` linkw at gcc dot gnu.org
2020-04-02  6:28 ` linkw at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94449-4-iUIJ7iacYV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).