From: Rich Felker <dalias@libc.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: RFC: [PATCH] x86: Add -mzero-caller-saved-regs=[skip|used|all]
Date: Thu, 27 Sep 2018 14:04:00 -0000 [thread overview]
Message-ID: <20180927140140.GP17995@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180926181029.GA20898@intel.com>
On Wed, Sep 26, 2018 at 11:10:29AM -0700, H.J. Lu wrote:
> Add -mzero-caller-saved-regs=[skip|used|all] command-line option and
> zero_caller_saved_regs("skip|used|all") function attribue:
Minor nit, but could this be named -mzero-call-clobbered-regs?
"Caller-saved" is a misnomer and inconsistent with other gcc usage.
For example -fcall-used-[reg] documents it as "an allocable register
that is clobbered by function calls". This is a piece of terminology
I've been trying to get fixed in educational materials so it would be
nice to avoid a new instance of it in gcc.
Rich
next prev parent reply other threads:[~2018-09-27 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 18:11 H.J. Lu
2018-09-27 11:01 ` Richard Biener
2018-09-27 13:08 ` H.J. Lu
2018-09-27 13:10 ` Szabolcs Nagy
2018-09-27 13:41 ` H.J. Lu
2018-09-27 15:13 ` Richard Biener
2018-09-27 19:41 ` H.J. Lu
2018-10-31 21:53 ` PATCH] x86: Add -mzero-caller-saved-regs=[skip|used-gpr|all-gpr|used|all] H.J. Lu
2018-11-29 23:16 ` PING [PATCH] " H.J. Lu
2018-12-21 13:23 ` PING^2 " H.J. Lu
2018-09-27 14:04 ` Rich Felker [this message]
2018-09-27 20:07 ` RFC: [PATCH] x86: Add -mzero-caller-saved-regs=[skip|used|all] H.J. Lu
2018-09-27 19:29 ` Florian Weimer
2018-09-27 19:51 ` H.J. Lu
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=20180927140140.GP17995@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=ubizjak@gmail.com \
/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).