public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: Jojo R <rjiejie@linux.alibaba.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: How to describe ‘earlyclobber’ explicitly for specific source operand ?
Date: Fri, 19 Nov 2021 15:54:49 -0600	[thread overview]
Message-ID: <0a17063d-9c7b-718c-ddae-7a5d96016953@linux.ibm.com> (raw)
In-Reply-To: <1b032580-97c7-41c5-9930-9a7354ae4151@Spark>

On 11/19/21 1:28 AM, Jojo R via Gcc wrote:
> 	We know gcc supply earlyclobber function to avoid register overlap,
> 
> 	but it can not describe explicitly for specific source operand, is it right ?

You add the early clobber to the OUTPUT operand(s) that can clobber any of the
input source operands.  You don't mark the source operands that could be clobbered.

Peter



  reply	other threads:[~2021-11-19 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eb109969-0133-49eb-b392-b35a065f12ba@Spark>
2021-11-19  7:28 ` Jojo R
2021-11-19 21:54   ` Peter Bergner [this message]
2021-11-22  6:40     ` Jojo R
2021-11-23 12:22       ` Richard Earnshaw

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=0a17063d-9c7b-718c-ddae-7a5d96016953@linux.ibm.com \
    --to=bergner@linux.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rjiejie@linux.alibaba.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).