This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] asm non-code template parts (alternative to asm inline)


Jakub Jelinek <jakub@redhat.com> writes:

> On Mon, Oct 15, 2018 at 01:53:09PM +0300, Alexander Monakov wrote:
>> On Mon, 15 Oct 2018, Jakub Jelinek wrote:
>> 
>> > On Mon, Oct 15, 2018 at 01:36:36PM +0300, Alexander Monakov wrote:
>> > > On Mon, 15 Oct 2018, Richard Biener wrote:
>> > > > 
>> > > > Oh, and I personally find %` ugly ;)  What non-alnum chars
>> > > > are taken by backends?
>> > > 
>> > > I think only double quote, backslash, backtick remain
>> > > unclaimed. And of course
>> > > ASCII \0 through \040 and \177 ;)
>> > 
>> > As has been said, the way microblaze claims non-alnum characters it doesn't
>> > support is just bogus, so we shouldn't consider them to be taken.
>> 
>> I understand - I've made an effort to manually go through the backends and
>> find characters they meaningfully handle in their print_operand hooks. In
>> particular MIPS handles all of []()<> (but %[ is special anyway, for
>> %[name] substitution).
>
> Ugh.  Wonder how %[name] then works on mips or if its %[ something %] works.

It's only provided for .md patterns (and probably predates the
named operands in inline asms), so in practice there's no problem.

Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]