public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109075] [13 Regression] rnflow hangs at -O3 Date: Thu, 09 Mar 2023 13:23:52 +0000 [thread overview] Message-ID: <bug-109075-4-wyV0tLgG05@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109075-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109075 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |INVALID CC| |pault at gcc dot gnu.org Known to work|12.2.0 | Keywords| |needs-bisection --- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> --- See comment at rnflow.f90:899 - As Richard Biener suggested to the list -fdefault-integer-8 fixes the problem but breaks tfft2 of the polyhedron suite. Better is: integer(8), parameter :: jmul = 843314861 ! multiplicateur integer(8), parameter :: jadd = 453816693 ! constante additive Cheers Paul
next prev parent reply other threads:[~2023-03-09 13:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-09 7:05 [Bug tree-optimization/109075] New: " tkoenig at gcc dot gnu.org 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 [this message] 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-wyV0tLgG05@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).