[llvm-dev] Unsigned int displaying as negative
Ryan Taylor via llvm-dev
llvm-dev at lists.llvm.org
Wed Feb 15 17:02:59 PST 2017
Tim, yes, I am on a very unique architecture, just about every instruction
has a signed and unsigned operation (ie, adds, addu, subs, subu, etc...)
and we handle signed and unsigned somewhat differently.
I'm not sure how we'll handle this yet, very worst case scenario is to
propagate the info from clang but that's not ideal, obviously.
Thanks for all the replies!
On Wed, Feb 15, 2017 at 5:16 PM, Tim Northover <t.p.northover at gmail.com>
> On 15 February 2017 at 10:19, Ryan Taylor via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > We have some code to determine if the operation is a signed or unsigned
> > operation in tablegen. Can anyone suggest a good way to get around this?
> I still think this is the basic problem. Unless you're on a really
> weird architecture it really doesn't matter whether an
> originally-written operation was signed or unsigned (with the
> already-represented exception of sdiv/udiv). It's probably best to
> take a step back and reassess this rather than ploughing on trying to
> preserve long-departed information.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev