[llvm-dev] constant string as an assembly operand

Sky Flyer via llvm-dev llvm-dev at lists.llvm.org
Fri Nov 6 02:30:52 PST 2015


I found the problem. In my asm parser, it could not distinguish between
AsmKind::String and AsmKind::Identifier.
My solution: I made a register class with a member with the name of the
constant string.

On Thu, Nov 5, 2015 at 4:50 PM, Tom Stellard <tom at stellard.net> wrote:

> On Thu, Nov 05, 2015 at 04:43:35PM +0100, Sky Flyer wrote:
> > Hi Tom,
> >
> > Thanks.
> > It should be always ABC.
> > What should be the iops? just (ins i8imm:$val)? what would be the
> > placeholder for a constant string in "ins"?
> >
>
> You shouldn't need to add anything to ins for this.
>
> -Tom
>
> >
> >
> > On Thu, Nov 5, 2015 at 4:33 PM, Tom Stellard <tom at stellard.net> wrote:
> >
> > > On Thu, Nov 05, 2015 at 03:20:45PM +0100, Sky Flyer via llvm-dev wrote:
> > > > Hello all,
> > > >
> > > > how can one can describe a constant string as an operand in the
> assembly
> > > > instruction?
> > > >
> > > > for example imagine this instruction:
> > > >
> > > > xyz 14 ABC
> > > >
> > > > where "xyz" is the operator, 14 is an immediate value, and because of
> > > > assembly dialect, there should be a constant string with the value
> of ABC
> > > > follow the immediate value. How is this possible?
> > > >
> > > > What should be the dat describing the instruction?
> > > >
> > > > string asm = "xyz $val ABC"
> > >
> > > Can this be an arbitrary string or will it always be ABC?  If it's the
> > > later,
> > > then what you've posted above should work for the asm string.
> > >
> > > -Tom
> > >
> > > > dag iops = (ins i8imm:val, ... )
> > > >
> > > >
> > > > Cheers,
> > > > ES
> > >
> > > > _______________________________________________
> > > > LLVM Developers mailing list
> > > > llvm-dev at lists.llvm.org
> > > > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> > >
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151106/207f88af/attachment.html>


More information about the llvm-dev mailing list