Do we support Not ANSI C compiler?

[Martin Liška]

On 5/9/22 11:22, Pedro Alves wrote:
> On 2022-05-09 09:49, Martin Liška wrote:
>> Hi.
>>
>> I noticed ./include/ansidecl.h contains not ANSI C path:
>>
>> #else	/* Not ANSI C.  */
>>
>> #define PTR		char *
>>
>> /* some systems define these in header files for non-ansi mode */
>> #undef const
>> #undef volatile
>> #undef signed
>> #undef inline
>> #define const
>> #define volatile
>> #define signed
>> #define inline
>>
>> #endif	/* ANSI C.  */
>>
>> And my question is if we really support such compilers or can we remove the hunk?
> 
> Given:
> 
>   - GCC requires C++11 nowadays,
>   - GDB requires C++11 nowadays,
>   - Binutils requires C99 nowadays (for over a year),
> 
> I'd think that no, we no longer support such compilers and we can remove the hunk.

All right. Thus I've just pushed sync from GCC.

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ansidecl.h-sync-from-GCC.patch
Type: text/x-patch
Size: 2743 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20220509/d7855b25/attachment.bin>