[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/3] yacc: compute the best type for the state number
From: |
Théophile Ranquet |
Subject: |
Re: [PATCH 0/3] yacc: compute the best type for the state number |
Date: |
Fri, 25 Oct 2019 16:15:54 +0200 |
Hi Paul,
On Tue, Oct 1, 2019 at 10:35 AM Paul Eggert <address@hidden> wrote:
>
> In other GNU applications, we've been moving away from using unsigned types
> due
> to their confusing behavior (particularly when comparing signed vs unsigned),
> and because modern tools such as 'gcc -fsanitize=undefined' can check for
> signed
> integer overflow but (obviously) not for unsigned integer overflow.
This sounds interesting and I would love reading what people have to
say about this. However, I have failed at finding any such discussion
or source. Could you perhaps share a few pointers?
Best regards,
Re: [PATCH 0/3] yacc: compute the best type for the state number, Paul Eggert, 2019/10/05
Re: [PATCH 0/3] yacc: compute the best type for the state number,
Théophile Ranquet <=