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/105559] New: -g and -O3 cause timeout
Date: Wed, 11 May 2022 10:16:12 +0000	[thread overview]
Message-ID: <bug-105559-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105559
           Summary: -g and -O3 cause timeout
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 52952
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52952&action=edit
C source code

For the attached C code, flags -g and -O3 cause a timeout:

$ time /home/dcb/gcc/results/bin/gcc  -w -c -O3  bug809.i

real    0m0.656s
user    0m0.587s
sys     0m0.032s
$ (ulimit -t 300; time /home/dcb/gcc/results/bin/gcc  -w -c -g -O3  bug809.i)
gcc: fatal error: Killed signal terminated program cc1
compilation terminated.

real    5m14.868s
user    4m57.685s
sys     0m2.265s
$ (ulimit -t 300; time /home/dcb/gcc/results/bin/gcc  -w -c -g -O2  bug809.i)

real    0m0.732s
user    0m0.683s
sys     0m0.024s
$ /home/dcb/gcc/results/bin/gcc -v 2>&1 | fgrep exp
gcc version 13.0.0 20220510 (experimental) (60ab3d0f2d9f9504) 
$

             reply	other threads:[~2022-05-11 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 10:16 dcb314 at hotmail dot com [this message]
2022-05-11 10:31 ` [Bug c/105559] " dcb314 at hotmail dot com
2022-05-11 10:41 ` [Bug c/105559] [12/13 Regression] -g and -O3 cause timeout since r12-156-g8d4c374c4419a875 marxin at gcc dot gnu.org
2022-05-11 11:06 ` rguenth at gcc dot gnu.org
2022-05-11 11:34 ` [Bug rtl-optimization/105559] " rguenth at gcc dot gnu.org
2022-05-11 11:40 ` rguenth at gcc dot gnu.org
2022-05-11 12:34 ` cvs-commit at gcc dot gnu.org
2022-05-11 12:59 ` [Bug rtl-optimization/105559] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-11 15:46 ` dcb314 at hotmail dot com
2022-05-12  6:47 ` rguenther at suse dot de
2022-05-19 12:47 ` cvs-commit at gcc dot gnu.org
2022-05-19 14:03 ` [Bug rtl-optimization/105559] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-05-27  9:48 ` [Bug rtl-optimization/105559] [10 " rguenth at gcc dot gnu.org
2022-05-27 13:15 ` cvs-commit at gcc dot gnu.org
2022-05-27 13:15 ` 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-105559-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).