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/98552] Make more use of __builtin_undefined for assuring that variables do not change Date: Sat, 09 Jan 2021 11:44:04 +0000 [thread overview] Message-ID: <bug-98552-4-rLO05fjhbu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98552-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98552 --- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Yes, I think that translating a DO loop into something like int i; for (i=0; i<n; i++) { const int j = i; /* Use j from here on where i is referenced. */ } might solve a few of the issues in DO loop optimization.
next prev parent reply other threads:[~2021-01-09 11:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-05 22:09 [Bug tree-optimization/98552] New: " tkoenig at gcc dot gnu.org 2021-01-05 22:10 ` [Bug tree-optimization/98552] " tkoenig at gcc dot gnu.org 2021-01-06 2:26 ` tobi at gcc dot gnu.org 2021-01-06 8:04 ` tkoenig at gcc dot gnu.org 2021-01-06 8:08 ` tobi at gcc dot gnu.org 2021-01-09 11:44 ` tkoenig at gcc dot gnu.org [this message] 2021-12-23 9:51 ` pinskia 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-98552-4-rLO05fjhbu@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).