Thx!
Your change is fine. Please go ahead
Sun
On Thu, Apr 14, 2011 at 2:33 PM, Yiran Wang wrote:
> The SGI document on WHIRL also mentioned this OPR.
> yiran
>
> On Thu, Apr 14, 2011 at 2:31 PM, Yiran Wang wrote:
>>
>> I do not know. But, it seems like the operator is not new at all, but
>> some
The SGI document on WHIRL also mentioned this OPR.
yiran
On Thu, Apr 14, 2011 at 2:31 PM, Yiran Wang wrote:
> I do not know. But, it seems like the operator is not new at all, but
> somebody (probably PathScale?) use it in some different way here.
> OPR_NEG = 87,
> OPR_NMADD = 88,
> OPR_NMSU
I do not know. But, it seems like the operator is not new at all, but
somebody (probably PathScale?) use it in some different way here.
OPR_NEG = 87,
OPR_NMADD = 88,
OPR_NMSUB = 89,
OPR_OPTPARM = 90,
OPR_OPT_CHI = 91,
OPR_OPT_RESERVE2 = 92,
OPR_PAREN = 93,
OPR_PARM = 94,
OPR_PICCALL = 95,
sorry, what does this OPR_PAREN opcode mean?
Sun
On Wed, Apr 13, 2011 at 11:13 AM, Yiran Wang wrote:
> Hi,
> could a gatekeeper please review this patch?
>
> This change is to deal with the OPR_PAREN nodes in this subroutine,
> which is inserted by simd-mark-code phase.
>
> Best Regards,
> yiran
Hi,
could a gatekeeper please review this patch?
This change is to deal with the OPR_PAREN nodes in this subroutine,
which is inserted by simd-mark-code phase.
Best Regards,
yiran
Index: osprey/be/lno/scalar_expand.cxx
===
--- ospre
