[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: |
Paul Eggert |
Subject: |
Re: [PATCH 0/3] yacc: compute the best type for the state number |
Date: |
Sat, 5 Oct 2019 02:21:28 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 10/1/19 1:35 AM, Paul Eggert wrote:
Actually those arrays use int_fast16_t not int16_t, as C99/C11/C18 does not
require support for int16_t. It could well be more efficient for them to use
int_least16_t instead, for better caching
Attached is a proposed patch to implement this for Bison. This patch also fixes
some portability problems for odd machines like the TI TMS320C55x where
'unsigned char', 'unsigned short', and 'unsigned' are all the same width (which
C allows), and where picky -Wconversion compilers warn about assigning an
unsigned char value to an int variable.
Comments welcome; I haven't installed this.
0001-Use-least-types-for-integers-in-Yacc-tables.txt
Description: Text document
- Re: [PATCH 0/3] yacc: compute the best type for the state number, (continued)
- 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, Akim Demaille, 2019/10/05
- 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, Paul Eggert, 2019/10/05
- Re: [PATCH 0/3] yacc: compute the best type for the state number, Akim Demaille, 2019/10/05
- Re: [PATCH 0/3] yacc: compute the best type for the state number, Akim Demaille, 2019/10/05
- 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,
Paul Eggert <=
Re: [PATCH 0/3] yacc: compute the best type for the state number, Théophile Ranquet, 2019/10/25