This is the mail archive of the gcc@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: how can I write a right V32QI Unpack Low Data insn pattern?


On 02/03/2011 15:14, Ian Lance Taylor wrote:
> Dave Korn writes:
> 
>> On 02/03/2011 07:56, Liu wrote:
>>
>>> The wrong code is :
>>>  L9284: ATTRIBUTE_UNUSED_LABEL
>>>   x3 = XEXP (x2, {);
>>>   if (x3 == const_int_rtx[MAX_SAVED_CONST_INT + (13)])
>>>     goto L9285;
>>>   goto ret0;
>>   Well, that's coming from here:
>>
>>       else
>> 	printf ("%sx%d = XEXP (x%d, %c);\n",
>> 		indent, depth + 1, depth, newpos[depth]);
>>       ++depth;
> 
> Interesting.  Looks you have a define_insn which has too many entries.
> It can only have 26 elements, but, annoyingly, genrecog doesn't check
> for that.
> 
> It's a bit odd to have more than 26 elements.  Do you have any
> incredibly large define_insn patterns?

  It's that huge parallel full of (const_int)s that OP quoted at us in the
first post.

    cheers,
      DaveK


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