public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109192] New: timeout with -g -O3 -fno-var-tracking ? Date: Sun, 19 Mar 2023 10:20:44 +0000 [thread overview] Message-ID: <bug-109192-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 Bug ID: 109192 Summary: timeout with -g -O3 -fno-var-tracking ? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 54705 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54705&action=edit C source code The attached C code can't be compiled in ten minutes, when -O3 -fno-var-tracking is used: $ (ulimit -t 600; time /home/dcb36/gcc/results/bin/gcc -w -c -O3 -fno-var-tracking bug898.c) gcc: fatal error: Killed signal terminated program cc1 compilation terminated. real 10m6.003s user 9m59.649s sys 0m0.103s It is fine when -O3 is replaced by -O2: $ (ulimit -t 600; time /home/dcb36/gcc/results/bin/gcc -w -c -O2 -fno-var-tracking bug898.c) real 0m0.453s user 0m0.434s sys 0m0.014s The bug first seems to occur sometime between 20230101 and 20230221. $ for i in ~/gcc/results.20230*/bin/gcc; do echo $i; (ulimit -t 60; time $i -c -w -O3 -fno-var-tracking bug898.c); done /home/dcb36/gcc/results.20230101/bin/gcc real 0m1.140s user 0m0.678s sys 0m0.021s /home/dcb36/gcc/results.20230221.asan.ubsan/bin/gcc gcc: fatal error: Killed signal terminated program cc1 compilation terminated. real 1m0.606s user 0m59.990s sys 0m0.016s Git hashes are g:4f1314f547f69d3a2b1f16ce301267e3bfb4e427 and g:a804419c89db9e1c, a range of some 1,800 commits.
next reply other threads:[~2023-03-19 10:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-19 10:20 dcb314 at hotmail dot com [this message] 2023-03-19 16:56 ` [Bug middle-end/109192] timeout with " dcb314 at hotmail dot com 2023-03-19 17:18 ` dcb314 at hotmail dot com 2023-03-19 17:18 ` dcb314 at hotmail dot com 2023-03-19 19:11 ` [Bug tree-optimization/109192] [13 Regression] timeout with -O3 -fno-var-tracking since r13-5579 pinskia at gcc dot gnu.org 2023-03-20 10:25 ` [Bug tree-optimization/109192] [13 Regression] timeout with -O3 " rguenth at gcc dot gnu.org 2023-03-20 10:35 ` rguenth at gcc dot gnu.org 2023-03-20 20:20 ` amacleod at redhat dot com 2023-03-21 10:33 ` rguenth at gcc dot gnu.org 2023-03-21 14:15 ` cvs-commit at gcc dot gnu.org 2023-03-21 14:15 ` amacleod at redhat dot com 2023-03-21 14:20 ` rguenth at gcc dot gnu.org 2023-03-28 7:52 ` chenglulu at loongson dot cn 2023-03-28 8:07 ` chenglulu at loongson dot cn 2023-03-28 13:22 ` amacleod at redhat dot com 2023-03-30 1:04 ` chenglulu at loongson dot cn
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-109192-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: linkBe 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).