bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/5138] Bit range mismatch in config/tc-cris.c


From: karvjorm at users dot sourceforge dot net
Subject: [Bug gas/5138] Bit range mismatch in config/tc-cris.c
Date: 9 Oct 2007 05:09:20 -0000

------- Additional Comments From karvjorm at users dot sourceforge dot net  
2007-10-09 05:09 -------
(In reply to comment #1)
> Well, it's 8-bit signed *and* 8-bit unsigned: perhaps saying 
> "not in 8-bit signed or unsigned range" would sound better to you?
> If you have a better wording to suggest, feel free.
> 
> brgds, H-P

Yes, that is one way to get around that, but there are still holes in that error
message. If it is a signed number, we don't catch values between 127...255 and
if it is an unsigned number, we don't catch values between -128 and 0. And there
is no way to know, which one we have, I suppose. If there are many immediate
values, one could always record the range of values and if most values are
either in range 0...127 or 128...255 we can suppose that the immediate value is
 unsigned value and values below zero should be illegal. But if an unsigned
value is never over 127 or the first value we record is illegal, this kind of
intelligence does not work. If we cannot warn about "hole" values, this single
error message is still a bit limited, even in its extended format.




-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5138

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]