Re: [PATCH] C/C++: don't suggest implementation names as spelling fixes (PR c/83236)

2017-12-01 Thread Jakub Jelinek
On Fri, Dec 01, 2017 at 04:48:20PM -0500, David Malcolm wrote: > PR c/83236 reports an issue where the C FE unhelpfully suggests the use > of glibc's private "__ino_t" type when it fails to recognize "ino_t": > > $ cat > test.c < #include > ino_t inode; > EOF > $ gcc -std=c89 -fsyntax-only test.c

[PATCH] C/C++: don't suggest implementation names as spelling fixes (PR c/83236)

2017-12-01 Thread David Malcolm
PR c/83236 reports an issue where the C FE unhelpfully suggests the use of glibc's private "__ino_t" type when it fails to recognize "ino_t": $ cat > test.c < ino_t inode; EOF $ gcc -std=c89 -fsyntax-only test.c test.c:2:1: error: unknown type name 'ino_t'; did you mean '__ino_t'? ino_t inode; ^