From: Mike Stump <mikestump@comcast.net>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org, Vladimir Makarov <vmakarov@redhat.com>
Subject: Re: -fuse-caller-save - Collect register usage information
Date: Thu, 16 Oct 2014 22:10:00 -0000 [thread overview]
Message-ID: <A9CDAD0D-3ECB-444D-9558-8713559532C4@comcast.net> (raw)
In-Reply-To: <5440387C.7060202@mentor.com>
On Oct 16, 2014, at 2:28 PM, Tom de Vries <Tom_deVries@mentor.com> wrote:
> So I'd say the documentation is in fact correct.
Agreed. I was confused. Apparently my mind likes to think in volatile and non-volatile (call-clobbered and non-call-clobbered) and I managed to map it wrong in my mind and not catch that fact I mapped them wrong.
> So, let's a generate a list of option names.
> Any preferences, alternatives?
So, since I was confused, my primary reason for not liking the option name was misguided.
next prev parent reply other threads:[~2014-10-16 22:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 19:22 fuse-caller-save - hook format Tom de Vries
2014-04-16 19:47 ` Richard Sandiford
2014-04-16 21:23 ` Jeff Law
2014-04-17 15:21 ` Vladimir Makarov
2014-04-17 15:35 ` Richard Sandiford
2014-04-17 16:49 ` Vladimir Makarov
2014-04-22 15:18 ` Tom de Vries
2014-04-22 15:31 ` Richard Sandiford
2014-04-22 16:10 ` Tom de Vries
2014-04-22 16:23 ` Richard Sandiford
2014-04-22 17:15 ` Tom de Vries
2014-04-23 8:54 ` Richard Earnshaw
2014-04-22 16:57 ` Add call_fusage_contains_non_callee_clobbers hook Tom de Vries
2014-04-23 15:16 ` Richard Sandiford
2014-04-24 7:23 ` Tom de Vries
2014-05-05 15:45 ` Vladimir Makarov
2014-04-23 10:49 ` -fuse-caller-save - Collect register usage information Tom de Vries
2014-04-23 15:10 ` Vladimir Makarov
2014-04-23 15:20 ` Richard Sandiford
2014-04-26 13:26 ` Tom de Vries
2014-05-12 13:28 ` [PING] " Tom de Vries
2014-05-17 10:52 ` Eric Botcazou
2014-05-19 14:30 ` Tom de Vries
2014-05-20 16:36 ` Eric Botcazou
2014-05-25 0:43 ` Jan Hubicka
2014-05-28 22:42 ` Bill Schmidt
2014-05-29 8:43 ` Tom de Vries
2014-06-19 5:13 ` Richard Henderson
2014-06-19 12:40 ` Tom de Vries
2014-06-19 15:36 ` Richard Henderson
2014-06-19 16:06 ` Tom de Vries
2014-06-19 16:26 ` Richard Henderson
2014-06-19 19:36 ` Jan Hubicka
2014-06-19 19:45 ` Richard Henderson
2014-07-13 12:18 ` Tom de Vries
2014-07-13 13:25 ` Jan Hubicka
2014-05-25 0:34 ` Jan Hubicka
2014-10-10 21:58 ` Mike Stump
2014-10-11 12:44 ` Eric Botcazou
2014-10-16 21:33 ` Tom de Vries
2014-10-16 21:54 ` Eric Botcazou
2014-10-17 11:00 ` Tom de Vries
2014-10-17 11:05 ` Richard Biener
2014-10-17 15:51 ` Jeff Law
2014-10-17 17:33 ` Mike Stump
2014-10-17 19:53 ` Eric Botcazou
2014-10-19 14:14 ` Tom de Vries
2014-10-20 17:23 ` Eric Botcazou
2014-10-16 22:10 ` Mike Stump [this message]
2014-04-23 12:27 ` Add clobber_reg Tom de Vries
2014-04-24 15:01 ` Eric Botcazou
2014-04-23 13:20 ` Add post_expand_call_insn hook Tom de Vries
2014-04-24 15:31 ` Eric Botcazou
2014-04-29 9:04 ` Tom de Vries
2014-04-29 19:00 ` Richard Henderson
2014-04-29 23:48 ` Tom de Vries
2014-04-25 13:20 ` -fuse-caller-save - Enable for MIPS Tom de Vries
2014-04-25 13:35 ` Richard Sandiford
2014-04-26 12:15 ` Tom de Vries
2014-04-27 10:30 ` Richard Sandiford
2014-04-27 23:49 ` Tom de Vries
2014-04-28 10:29 ` Richard Sandiford
2014-04-28 10:48 ` Tom de Vries
2014-04-28 12:14 ` Tom de Vries
2014-04-28 15:01 ` Richard Sandiford
2014-04-28 14:55 ` Richard Sandiford
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=A9CDAD0D-3ECB-444D-9558-8713559532C4@comcast.net \
--to=mikestump@comcast.net \
--cc=Tom_deVries@mentor.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.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).