public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109075] New: [13 Regression] rnflow hangs at -O3 Date: Thu, 09 Mar 2023 07:05:11 +0000 [thread overview] Message-ID: <bug-109075-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109075 Bug ID: 109075 Summary: [13 Regression] rnflow hangs at -O3 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: tkoenig at gcc dot gnu.org Target Milestone: --- rnflow from the pb11 Polyhedron benchmark hangs at -O3 with recent trunk, gcc-Version 13.0.1 20230308 (experimental) [master revision e87559d202d:f4e6da6e8ac:36ec54aac7da134441c83248e14825381b8d6f17] (GCC) Compiling with -O3 -g, running under gdb and interrupting the program sometime after (gdb) r rnflow.in Starting program: /tmp/a.out rnflow.in 0: 0: 0.000 -> Read sequence 0: 0: 0.213 -> extract extrema 0: 0: 0.215 -> Generate raw transitions counts 0: 0: 0.221 -> Compute Markov matrix 0: 0: 0.221 -> Calculate theoretical rainflow 0: 0: 7.487 -> Simulate random markov sequences ^C Program received signal SIGINT, Interrupt. 0x0000000000402149 in minlst (ipos2=<optimized out>, ipos1=<optimized out>) at rnflow.f90:3698 3698 if (xxtrt (ipos) < xxtrt (minlst)) then (gdb) l 3693 ! 3694 ! .. dernier minimum de xxtrt entre ipos1 et ipos2 3695 ! 3696 minlst = ipos2 3697 do ipos = ipos2 - 1, ipos1, -1 3698 if (xxtrt (ipos) < xxtrt (minlst)) then 3699 minlst = ipos 3700 endif 3701 enddo 3702 end function minlst where it goes into an endless loop. This happens both on x86_64 and on POWER.
next reply other threads:[~2023-03-09 7:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-09 7:05 tkoenig at gcc dot gnu.org [this message] 2023-03-09 7:05 ` [Bug tree-optimization/109075] " tkoenig at gcc dot gnu.org 2023-03-09 7:06 ` tkoenig at gcc dot gnu.org 2023-03-09 7:07 ` tkoenig at gcc dot gnu.org 2023-03-09 7:08 ` tkoenig at gcc dot gnu.org 2023-03-09 9:08 ` tkoenig at gcc dot gnu.org 2023-03-09 9:26 ` jakub at gcc dot gnu.org 2023-03-09 9:36 ` tkoenig at gcc dot gnu.org 2023-03-09 10:13 ` jakub at gcc dot gnu.org 2023-03-09 10:22 ` rguenth at gcc dot gnu.org 2023-03-09 13:23 ` pault at gcc dot gnu.org 2023-03-09 13:29 ` pault 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-109075-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).