public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108687] [13 Regression] Non-termination since r13-5630-g881bf8de9b0
Date: Thu, 09 Feb 2023 15:50:50 +0000	[thread overview]
Message-ID: <bug-108687-4-U4KiadLyY1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108687-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Macleod <amacleod at redhat dot com> ---
My cross compiler doesn't seem to exhibit this behaviour. It simply compiles
this as a quite short program.

It looks like it in the DOM pass.. could you try it with:


-fdump-tree-all-detail --param=ranger-debug=all

stop it very shortly after it runs, if it is in a loop of some sort, one of
these output files is going to grow very quickly.. probably one of:

t.c*dom2 or
t.c*dom3

I might be able to tell from the debug output where the cycle is.  Doesnt need
to be attached here, you could just email it to me.

Or is there some other way to reproduce this?  I don't have access to a s390 at
the moment. Any chance the compiler is miscompiled?   does the same thing
happen with a stage 1 compiler?

  parent reply	other threads:[~2023-02-09 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 19:17 [Bug middle-end/108687] New: Non-termination since gcc-13-5630-g881bf8de9b0 stefansf at linux dot ibm.com
2023-02-06 19:20 ` [Bug middle-end/108687] Non-termination since r13-5630-g881bf8de9b0 pinskia at gcc dot gnu.org
2023-02-06 19:21 ` stefansf at linux dot ibm.com
2023-02-06 19:28 ` stefansf at linux dot ibm.com
2023-02-06 19:29 ` stefansf at linux dot ibm.com
2023-02-06 19:45 ` [Bug middle-end/108687] [13 Regression] " pinskia at gcc dot gnu.org
2023-02-06 21:11 ` [Bug tree-optimization/108687] " jakub at gcc dot gnu.org
2023-02-09 15:50 ` amacleod at redhat dot com [this message]
2023-02-09 18:27 ` stefansf at linux dot ibm.com
2023-02-09 18:39 ` amacleod at redhat dot com
2023-02-09 20:07 ` stefansf at linux dot ibm.com
2023-02-09 23:41 ` amacleod at redhat dot com
2023-02-10  9:44 ` stefansf at linux dot ibm.com
2023-02-10 14:49 ` cvs-commit at gcc dot gnu.org
2023-02-10 14:54 ` amacleod at redhat dot com

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-108687-4-U4KiadLyY1@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).