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 debug/108843] timeout with -g -O3 since r9-2635-g78ea9abc2018243a
Date: Fri, 15 Mar 2024 11:28:14 +0000	[thread overview]
Message-ID: <bug-108843-4-MYH0pGSEnY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108843-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from David Binderman <dcb314 at hotmail dot com> ---
Created attachment 57711
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57711&action=edit
C source code

Another test case.

foundBugs $ (ulimit -t 60; time ~/gcc/results/bin/gcc -c -w -O3 bug1023.c)
real    0m0.456s
user    0m0.435s
sys     0m0.019s

foundBugs $ (ulimit -t 60; time ~/gcc/results/bin/gcc -c -w -g -O3 bug1023.c)
gcc: fatal error: Killed signal terminated program cc1
compilation terminated.
real    1m0.363s
user    0m59.555s
sys     0m0.524s

foundBugs $ (ulimit -t 60; time ~/gcc/results/bin/gcc -c -w -g -O3
-fno-var-tracking bug1023.c)
real    0m6.269s
user    0m5.620s
sys     0m0.502s
foundBugs $

      parent reply	other threads:[~2024-03-15 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18  9:11 [Bug debug/108843] New: timeout with -g -O3 ? dcb314 at hotmail dot com
2023-02-18  9:18 ` [Bug debug/108843] " dcb314 at hotmail dot com
2023-02-20  8:24 ` rguenth at gcc dot gnu.org
2023-02-23 15:37 ` marxin at gcc dot gnu.org
2023-02-23 15:46 ` [Bug debug/108843] timeout with -g -O3 since r9-2635-g78ea9abc2018243a marxin at gcc dot gnu.org
2024-03-15 11:28 ` dcb314 at hotmail dot com [this message]

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-108843-4-MYH0pGSEnY@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).