public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "19373742 at buaa dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111554] New: Timeout with with "-O3 -fno-dse -fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce -fno-tree-dse"
Date: Sat, 23 Sep 2023 16:57:28 +0000 [thread overview]
Message-ID: <bug-111554-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111554
Bug ID: 111554
Summary: Timeout with with "-O3 -fno-dse -fno-inline
-fno-store-merging -fno-toplevel-reorder -fno-tree-dce
-fno-tree-dse"
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: 19373742 at buaa dot edu.cn
Target Milestone: ---
Created attachment 55974
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55974&action=edit
The preprocessed file
*******************************************************************************
OS and Platform:
Ubuntu 20.04.4 LTS
*******************************************************************************
gcc version:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/home/cuisk/ctc/gcc-releases/gcc-14/bin/gcc
COLLECT_LTO_WRAPPER=/home/cuisk/ctc/gcc-releases/gcc-14/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ./configure --prefix=/home/cuisk/ctc/gcc-releases/gcc-14
--disable-multilib --enable-language=c,c++
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230917 (experimental) (GCC)
*******************************************************************************
Command Lines:
$ (ulimit -t 60; gcc -I /home/csmith/include/csmith-2.3.0 -O3 -fno-dse
-fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce
-fno-tree-dse a.c -o tle.o)
gcc: fatal error: Killed signal terminated program cc1
compilation terminated.
$ (ulimit -t 60; /home/cuisk/ctc/gcc-releases/gcc-14/bin/gcc -I
/home/cuisk/ctc/csmith/include/csmith-2.3.0 -save-temps /home/cuisk/gcc/tmp/a.c
-o tle2.o 2>tle.out)
$./tle2.o
checksum = 0
next reply other threads:[~2023-09-23 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:57 19373742 at buaa dot edu.cn [this message]
2023-09-23 16:57 ` [Bug c/111554] " 19373742 at buaa dot edu.cn
2023-09-23 17:02 ` [Bug rtl-optimization/111554] " pinskia at gcc dot gnu.org
2023-10-22 23:46 ` [Bug rtl-optimization/111554] [12/13/14 regression] " sjames at gcc dot gnu.org
2023-10-22 23:55 ` pinskia at gcc dot gnu.org
2023-10-23 3:27 ` [Bug rtl-optimization/111554] [12/13/14 regression] Timeout with with "-O3 -fno-dse -fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce -fno-tree-dse" since r12-2097-g9f34b780b0461e sjames at gcc dot gnu.org
2023-10-23 3:48 ` pinskia at gcc dot gnu.org
2023-10-23 3:53 ` pinskia at gcc dot gnu.org
2023-10-23 4:52 ` pinskia at gcc dot gnu.org
2023-10-23 5:01 ` pinskia at gcc dot gnu.org
2023-10-23 9:54 ` rguenth at gcc dot gnu.org
2023-10-30 13:47 ` mkuvyrkov at gcc dot gnu.org
2023-11-19 8:47 ` mkuvyrkov at gcc dot gnu.org
2023-11-20 8:18 ` rguenth at gcc dot gnu.org
2023-11-20 12:09 ` mkuvyrkov at gcc dot gnu.org
2024-01-17 7:48 ` cvs-commit at gcc dot gnu.org
2024-01-17 8:42 ` [Bug rtl-optimization/111554] [12/13 " rguenth at gcc dot gnu.org
2024-01-17 10:18 ` mkuvyrkov at gcc dot gnu.org
2024-01-17 12:35 ` rguenth 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-111554-4@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).