Re: [PATCH v2] c, analyzer: support named constants in analyzer [PR106302]

2022-11-14 Thread Marek Polacek via Gcc-patches
On Fri, Nov 11, 2022 at 10:23:10PM -0500, David Malcolm wrote: > Changes since v1: ported the doc changes from texinfo to sphinx > > Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. > > Are the C frontend parts OK for trunk? (I can self-approve the > analyzer parts) Sorry for the

Re: [PATCH v2] c, analyzer: support named constants in analyzer [PR106302]

2022-11-11 Thread David Malcolm via Gcc-patches
On Fri, 2022-11-11 at 22:23 -0500, David Malcolm wrote: > Changes since v1: ported the doc changes from texinfo to sphinx > > Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. > > Are the C frontend parts OK for trunk?  (I can self-approve the > analyzer parts) ...and FWIW, the foll

[PATCH v2] c, analyzer: support named constants in analyzer [PR106302]

2022-11-11 Thread David Malcolm via Gcc-patches
Changes since v1: ported the doc changes from texinfo to sphinx Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Are the C frontend parts OK for trunk? (I can self-approve the analyzer parts) Thanks Dave The analyzer's file-descriptor state machine tracks the access mode of open