public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <Tom_deVries@mentor.com>
To: <sellcey@cavium.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	richard.earnshaw	<richard.earnshaw@arm.com>
Subject: Re: [Patch] Document __builtin_extend_pointer
Date: Tue, 20 Mar 2018 12:13:00 -0000	[thread overview]
Message-ID: <6a8f42af-7413-5b55-2bd9-09244cca36ab@mentor.com> (raw)
In-Reply-To: <1519147981.6296.18.camel@cavium.com>

On 02/20/2018 06:33 PM, Steve Ellcey wrote:
> +@deftypefn {Built-in Function} Pmode __builtin_extend_pointer (void * x)
> +On targets where the user visible pointer size is different than the size
> +of an actual hardware address this function returns the extended user
> +pointer.  Targets where this is true included ILP32 mode on x86_64 or
> +Aarch64.  This function is mainly useful when writing inline assembly
> +code.
> +@var{addr}
> +@end deftypefn

Hi,

I think the "@var{addr}" bit is a pasto.

Thanks,
- Tom

  parent reply	other threads:[~2018-03-20 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 17:33 Steve Ellcey
2018-02-22  5:04 ` Jeff Law
2018-03-20 12:13 ` Tom de Vries [this message]
2018-03-20 21:00   ` Jeff Law

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=6a8f42af-7413-5b55-2bd9-09244cca36ab@mentor.com \
    --to=tom_devries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.earnshaw@arm.com \
    --cc=sellcey@cavium.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).