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 other/113399] [14 Regression] -ffold-mem-offsets should not be a target option
Date: Wed, 17 Jan 2024 16:29:54 +0000 [thread overview]
Message-ID: <bug-113399-4-RViXooygOx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113399-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113399
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ok, I'll bootstrap/regtest:
2024-01-17 Jakub Jelinek <jakub@redhat.com>
PR other/113399
* common.opt (ffold-mem-offset): Remove Target and Bool keywords, add
Common and Optimization.
--- gcc/common.opt.jj 2024-01-03 11:51:31.467732078 +0100
+++ gcc/common.opt 2024-01-17 17:22:05.975424001 +0100
@@ -1262,7 +1262,7 @@ Common Var(flag_cprop_registers) Optimiz
Perform a register copy-propagation optimization pass.
ffold-mem-offsets
-Target Bool Var(flag_fold_mem_offsets) Init(1)
+Common Var(flag_fold_mem_offsets) Init(1) Optimization
Fold instructions calculating memory offsets to the memory access instruction
if possible.
fcrossjumping
The removal of Bool is for consistency, there are no other common.opt nor
*/*.opt options using it.
next prev parent reply other threads:[~2024-01-17 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:25 [Bug other/113399] New: " gjl at gcc dot gnu.org
2024-01-15 13:37 ` [Bug other/113399] [14 Regression] " jakub at gcc dot gnu.org
2024-01-15 14:27 ` rguenth at gcc dot gnu.org
2024-01-15 14:40 ` jakub at gcc dot gnu.org
2024-01-15 14:41 ` jakub at gcc dot gnu.org
2024-01-17 14:57 ` law at gcc dot gnu.org
2024-01-17 16:29 ` jakub at gcc dot gnu.org [this message]
2024-01-18 7:45 ` cvs-commit at gcc dot gnu.org
2024-01-18 7:54 ` jakub 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-113399-4-RViXooygOx@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: link
Be 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).