From: Florian Weimer <fweimer@redhat.com>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: "Paul A. Clarke via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] [powerpc] Tighten contraints for asm constant parameters
Date: Tue, 19 Oct 2021 17:59:52 +0200 [thread overview]
Message-ID: <87o87lyphj.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20211019155853.GB104437@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com> (Paul A. Clarke's message of "Tue, 19 Oct 2021 10:58:53 -0500")
* Paul A. Clarke:
> I was too loose with my characterization of 'i', in contrast to 'n':
>
> | ‘n’
> | An immediate integer operand with a known numeric value is allowed.
> | Many systems cannot support assembly-time constants for operands less
> | than a word wide. Constraints for these operands should use ‘n’
> | rather than ‘i’.
>
> The cases changed by the patch require a *known numeric value*, as they are
> used as immediate values (hardcoded in the generated opcode).
>
> I will reword to:
> There are a few places where only known numeric values are acceptable for
> `asm` parameters, yet the constraint "i" is used. "i" can include
> "symbolic constants whose values will be known only at assembly time or
> later."
>
> Use "n" instead of "i" where known numeric values are required.
>
> Does that work better?
Yes, that explains the difference. Thanks!
Florian
next prev parent reply other threads:[~2021-10-19 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 15:14 Paul A. Clarke
2021-10-19 15:26 ` Florian Weimer
2021-10-19 15:58 ` Paul A. Clarke
2021-10-19 15:59 ` Florian Weimer [this message]
2021-10-29 19:26 ` Tulio Magno Quites Machado Filho
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=87o87lyphj.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=pc@us.ibm.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).