[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #51447] Sequence number comparisons invoke undefined b
From: |
Valery Ushakov |
Subject: |
[lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior |
Date: |
Thu, 13 Jul 2017 17:54:17 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 |
Follow-up Comment #6, bug #51447 (project lwip):
@abizjak - If you want to start nit-picking, you may at least try to be
careful about your own wording. Your summary claims "undefined behavior", but
then you quote the relevant part of the standard that says
"implementation-defined behavior".
So, basically you complain that lwip assumes 2-complement.
@mywave - converting -1 to u32_t is done by repeatedly adding
("mathematically") UINT32_MAX+1, so (after just one iteration) you will get
the expected 0xffffffff
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?51447>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Ambroz Bizjak, 2017/07/11
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Ambroz Bizjak, 2017/07/11
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Stian Sebastian Skjelstad, 2017/07/12
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Stian Sebastian Skjelstad, 2017/07/12
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Ambroz Bizjak, 2017/07/12
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Ambroz Bizjak, 2017/07/12
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior,
Valery Ushakov <=
- [lwip-devel] [bug #51447] Sequence number comparisons invoke undefined behavior, Ambroz Bizjak, 2017/07/13
- [lwip-devel] [bug #51447] Sequence number comparisons invoke implementation-defined behavior, Simon Goldschmidt, 2017/07/14
- [lwip-devel] [bug #51447] Sequence number comparisons invoke implementation-defined behavior, Simon Goldschmidt, 2017/07/14
- [lwip-devel] [bug #51447] Sequence number comparisons invoke implementation-defined behavior, Ambroz Bizjak, 2017/07/17