From: "Stefan Franke" <stefan@franke.ms>
To: <gcc-help@gcc.gnu.org>
Subject: Additional peephole pass(es)
Date: Mon, 20 Apr 2020 12:20:35 +0200 [thread overview]
Message-ID: <04d901d616fd$55668f50$0033adf0$@franke.ms> (raw)
Hi there,
is there a chance that a patch would be accepted if it adds (an) additional
peephole pass(es)?
I'm not content with the capabilities of the combine pass and a convenient
way would be to insert an additional pass in front/after the combine pass.
It's way easier to maintain than the spaghetti code in combine and ss long
there is nothing defined in the cpu's md file, the pass gets skipped, so the
overhead for non-users is almost non existent.
Right now I'm applying the same set as in the final peephole run, but I
would add a separate keyword per pass, e.g. peephole_precombine, etc. p.p.
Your thoughts?
/cheers Stefan
next reply other threads:[~2020-04-20 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 10:20 Stefan Franke [this message]
2020-04-20 17:34 ` Oleg Endo
2020-04-24 21:36 ` Segher Boessenkool
2020-04-25 4:04 ` Oleg Endo
2020-04-25 12:21 ` Segher Boessenkool
2020-04-24 21:07 ` Segher Boessenkool
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='04d901d616fd$55668f50$0033adf0$@franke.ms' \
--to=stefan@franke.ms \
--cc=gcc-help@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).