From: Pedro Alves <pedro@palves.net>
To: "Martin Liška" <mliska@suse.cz>, Binutils <binutils@sourceware.org>
Subject: Re: Do we support Not ANSI C compiler?
Date: Mon, 9 May 2022 10:22:39 +0100 [thread overview]
Message-ID: <70918576-c535-0218-720f-24ac44af4091@palves.net> (raw)
In-Reply-To: <99b5380e-8072-dd67-497d-94f72eee43c3@suse.cz>
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.
next prev parent reply other threads:[~2022-05-09 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 8:49 Martin Liška
2022-05-09 9:22 ` Pedro Alves [this message]
2022-05-09 12:01 ` Martin Liška
2022-05-10 1:44 ` Alan Modra
2022-05-10 1:47 ` bfd: remove use of PTR Alan Modra
2022-05-10 1:49 ` opcodes: " Alan Modra
2022-05-10 1:49 ` gas: " Alan Modra
2022-05-10 1:50 ` gprof: " Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70918576-c535-0218-720f-24ac44af4091@palves.net \
--to=pedro@palves.net \
--cc=binutils@sourceware.org \
--cc=mliska@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).