Displaying 5 results from an estimated 5 matches for "binarywithflagssdnode".
2017 Feb 15
2
Unsigned int displaying as negative
Thanks for your reply.
We are propagating sign info to tablegen currently using
BinaryWithFlagsSDNode.Flags.hasNoSignedWrap atm.
I imagine (I have not looked) they are printed according to instruction in
AsmPrinter.cpp (pure speculation).
I'm still confused as to why 0x7FFF is ok to match 16 bit int but not
0x8000?
Thanks.
On Wed, Feb 15, 2017 at 1:44 PM, Manuel Jacob <me at manueljacob....
2017 Feb 15
5
Unsigned int displaying as negative
...17 at 2:24 PM, Manuel Jacob <me at manueljacob.de>
>> wrote:
>>
>>> On 2017-02-15 19:54, Ryan Taylor wrote:
>>>
>>>> Thanks for your reply.
>>>>
>>>> We are propagating sign info to tablegen currently using
>>>> BinaryWithFlagsSDNode.Flags.hasNoSignedWrap atm.
>>>>
>>>
>>> Note that this flag doesn't indicate signedness of the operation. It
>>> just means that the optimizer or code generator can assume that no
>>> signed
>>> overflow will happen during the operati...
2017 Feb 15
4
Unsigned int displaying as negative
...;
{
let mayStore = 1;
let mayLoad = 1;
}
On Wed, Feb 15, 2017 at 2:24 PM, Manuel Jacob <me at manueljacob.de> wrote:
> On 2017-02-15 19:54, Ryan Taylor wrote:
>
>> Thanks for your reply.
>>
>> We are propagating sign info to tablegen currently using
>> BinaryWithFlagsSDNode.Flags.hasNoSignedWrap atm.
>>
>
> Note that this flag doesn't indicate signedness of the operation. It just
> means that the optimizer or code generator can assume that no signed
> overflow will happen during the operation. To get a better understanding
> of why this flag...
2014 Jul 09
3
[LLVMdev] Signed/Unsigned Instruction selection.
The sign information for binary operators is available in the llvm IR by the
'nsw' (no signed wrap) flag. Seems there is no use of this flag in the code
generation phase.
The sign information is no more available in the selection DAG.
So how can I generate different instructions for binary operators with
signed/unsigned operands in the assembler (e.g. mul/mulu)?
--
View this message in
2017 Feb 15
6
Unsigned int displaying as negative
I'm curious why 'unsigned short w = 0x8000' is displayed as -32768 in the
IR?
This propagates to the DAG and hence tablegen, where I am missing matching
on some immediates because the immediate is not being looked at as
unsigned? For example, we have no issue if instead of 0x8000 we use 0x7FFF,
then everything is fine, the match is fine.
I can understand that it's just being