From: Joseph Myers <joseph@codesourcery.com>
To: Maya Rashish <coypu@sdf.org>
Cc: <gcc-patches@gcc.gnu.org>, <gerald@pfeifer.com>
Subject: Re: [PATCH 1/2] Untangle stddef.h a little
Date: Tue, 19 Jun 2018 15:32:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806191528230.7791@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180204073846.GA17915@SDF.ORG>
On Sun, 4 Feb 2018, Maya Rashish wrote:
> Of the currently supported BSDs:
> - FreeBSD, doesn't have ansi.h or define _MACHINE_ANSI_H anywhere
> in its other headers since the long-gone 5.x release.
> - OpenBSD, DragonflyBSD don't have ansi.h either.
> - NetBSD, sole remaining with ansi.h
>
> Replace all the ifdef macros to be ifdef __NetBSD__ as it's the
> sole remaining user.
>
> Whether it is appropriate to make per-OS choices here is debatable,
> but this change allows for further future cleanup.
>
> This enables using the headers on netbsd archs that use different
> include guards for ansi.h, like ARM.
These two patches are OK, please commit.
(GCC officially removed support for FreeBSD versions before FreeBSD 5 with
r260852 | gerald | 2018-05-28 23:20:15 +0000 (Mon, 28 May 2018) | 5 lines
* config.gcc: Identify FreeBSD 3.x and 4.x as unsupported.
* config/freebsd-spec.h (FBSD_LIB_SPEC): Only consider FreeBSD 5
and later.
<https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01409.html>.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-19 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 7:38 Maya Rashish
2018-02-04 7:41 ` [PATCH 2/2] Simplify: combine cases for dfly+fbsd with vms coypu
2018-02-13 0:41 ` [PATCH 1/2] Untangle stddef.h a little coypu
2018-02-19 22:12 ` coypu
2018-03-01 2:43 ` coypu
2018-03-01 6:02 ` Kamil Rytarowski
2018-06-19 15:32 ` Joseph Myers [this message]
2018-06-19 22:08 ` coypu
2018-06-19 22:43 ` Gerald Pfeifer
2018-06-24 23:19 ` Gerald Pfeifer
2018-06-25 21:37 ` Jeff Law
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=alpine.DEB.2.20.1806191528230.7791@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=coypu@sdf.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).