public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: Should binutils require at least C99?
Date: Tue, 30 Mar 2021 12:44:53 +0100	[thread overview]
Message-ID: <43c77ac5-f8d4-5739-a3ae-64f6f3314a39@redhat.com> (raw)
In-Reply-To: <20210329003539.GD5425@bubble.grove.modra.org>

Hi Alan,

> I feel that it is reasonable nowadays to require a C99 compiler and
> library to build binutils.  Trying to support older systems that no
> one appears to test is a losing battle anyway.  For example, the s12z
> target requires stdbool.h and stdint.h, and many targets include
> string.h without concern for HAVE_STRING_H or STRING_WITH_STRINGS.
> 
> Does anyone object to formally dropping support for pre-C99?

Nope - I am firmly in favour of the idea.

Cheers
   Nick


  parent reply	other threads:[~2021-03-30 11:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  0:35 Alan Modra
2021-03-29  1:42 ` Mike Frysinger
2021-03-30  0:28   ` Fangrui Song
2021-03-30 11:44 ` Nick Clifton [this message]
2021-03-31  0:20   ` Include string.h in bfd.h and delete LITMEMCPY, LITSTRCPY Alan Modra
2021-03-31  0:23     ` Remove bfd_stdint.h Alan Modra
2021-03-31  0:24       ` Use stdbool.h Alan Modra
2021-03-31  0:26         ` Use bool in include Alan Modra
2021-03-31  0:28           ` Use bool in gprof Alan Modra
2021-03-31  0:31             ` Use bool in bfd Alan Modra
2021-03-31  0:32               ` Use bool in opcodes Alan Modra
2021-03-31  0:33                 ` Use bool in binutils Alan Modra
2021-03-31  0:34                   ` Use bool in ld Alan Modra
2021-03-31  0:34                     ` Use bool in gas 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=43c77ac5-f8d4-5739-a3ae-64f6f3314a39@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).