public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs) Date: Mon, 22 Apr 2024 08:08:39 +0000 [thread overview] Message-ID: <bug-114787-4-VjvAfiMyuD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114787-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It is the if (dump_file && (dump_flags & TDF_DETAILS) && max_loop_iterations_int (loop) >= 0) { fprintf (dump_file, "Loop %d iterates at most %i times.\n", loop->num, (int)max_loop_iterations_int (loop)); } if (dump_file && (dump_flags & TDF_DETAILS) && likely_max_loop_iterations_int (loop) >= 0) { fprintf (dump_file, "Loop %d likely iterates at most %i times.\n", loop->num, (int)likely_max_loop_iterations_int (loop)); } cases which trigger the different code generation with -fdump-tree-profile_estimate-details -O1, either of them; guess max_loop_iterations_int and likely_max_loop_iterations_int cache the results and while it doesn't change the IL from the profile_estimate pass, it changes the behavior of the cunroll pass later on.
next prev parent reply other threads:[~2024-04-22 8:08 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-20 10:53 [Bug tree-optimization/114787] New: " zhendong.su at inf dot ethz.ch 2024-04-20 10:59 ` [Bug tree-optimization/114787] [14 Regression] " jakub at gcc dot gnu.org 2024-04-20 14:22 ` law at gcc dot gnu.org 2024-04-20 22:03 ` [Bug target/114787] " pinskia at gcc dot gnu.org 2024-04-20 23:03 ` [Bug tree-optimization/114787] " pinskia at gcc dot gnu.org 2024-04-20 23:10 ` [Bug tree-optimization/114787] [13/14 " pinskia at gcc dot gnu.org 2024-04-20 23:37 ` pinskia at gcc dot gnu.org 2024-04-20 23:50 ` pinskia at gcc dot gnu.org 2024-04-22 7:39 ` jakub at gcc dot gnu.org 2024-04-22 7:49 ` jakub at gcc dot gnu.org 2024-04-22 8:08 ` jakub at gcc dot gnu.org [this message] 2024-04-22 8:24 ` pinskia at gcc dot gnu.org 2024-04-22 9:09 ` jakub at gcc dot gnu.org 2024-04-22 12:45 ` jakub at gcc dot gnu.org 2024-04-22 13:01 ` hubicka at gcc dot gnu.org 2024-04-24 6:12 ` rguenth at gcc dot gnu.org 2024-04-24 6:47 ` rguenth at gcc dot gnu.org 2024-04-24 8:13 ` cvs-commit at gcc dot gnu.org 2024-04-24 8:14 ` [Bug tree-optimization/114787] [13 " rguenth at gcc dot gnu.org 2024-04-24 14:38 ` hubicka at gcc dot gnu.org 2024-05-06 13:15 ` cvs-commit at gcc dot gnu.org 2024-05-06 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-114787-4-VjvAfiMyuD@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).