public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/101691] New: d: Use of LOOP_EXPR prevents removing no-op loops. Date: Fri, 30 Jul 2021 10:35:27 +0000 [thread overview] Message-ID: <bug-101691-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101691 Bug ID: 101691 Summary: d: Use of LOOP_EXPR prevents removing no-op loops. Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ibuclaw at gdcproject dot org Target Milestone: --- As observed on compiler explorer. https://d.godbolt.org/z/eM8Pv91eT The C, C++ (and Fortran?) front-ends lower loops as labels and gotos, which *is* optimized away. https://godbolt.org/z/8Yz9oqx63 --- void fun(int a, int b, int step) { for (int i = a; i < b; i += step) { } }
next reply other threads:[~2021-07-30 10:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-30 10:35 ibuclaw at gdcproject dot org [this message] 2021-07-30 20:47 ` [Bug d/101691] " pinskia at gcc dot gnu.org 2021-07-30 20:49 ` pinskia at gcc dot gnu.org 2022-07-08 8:54 ` ibuclaw at gdcproject dot 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-101691-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).