From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Nathan Sidwell <nathan@acm.org>,GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PTX] simplify calling struct
Date: Thu, 17 Dec 2015 22:59:00 -0000 [thread overview]
Message-ID: <BE16BE6D-3BFE-438F-9FBE-61D8BBBB8CD4@gmail.com> (raw)
In-Reply-To: <56716CEF.9060709@acm.org>
On December 16, 2015 2:53:51 PM GMT+01:00, Nathan Sidwell <nathan@acm.org> wrote:
>PTX's machine_function structure squirrels away the function type to
>calculate
>the presence of varadic args later, rather than calculate it
>immediately. It
>also uses an rtx field as a boolean. This patch reorganizes it with
>less
>verbose names and more apt types.
+ bool is_varadic; /* This call is varadic */
+ bool has_varadic; /* Current function has a varadic call. */
Just curious what varadic is? Is that maybe somehow related to variadic?
TIA,
>
>I also noticed that nvptx_hard_regno_mode_ok wasn't being used, so
>that's deleted.
>
>nathan
prev parent reply other threads:[~2015-12-17 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 13:53 Nathan Sidwell
2015-12-17 22:59 ` Bernhard Reutner-Fischer [this message]
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=BE16BE6D-3BFE-438F-9FBE-61D8BBBB8CD4@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.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).