public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
	Joseph Myers <joseph@codesourcery.com>,
	Andreas Tobler <andreast@FreeBSD.org>,
	Maya Rashish <coypu@sdf.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] Untangle stddef.h a little
Date: Mon, 25 Jun 2018 21:37:00 -0000	[thread overview]
Message-ID: <0df801b7-6e2c-9be7-4510-da7c8d5e13f5@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1806242345420.3747@anthias.pfeifer.com>

On 06/24/2018 05:19 PM, Gerald Pfeifer wrote:
> On Tue, 19 Jun 2018, Joseph Myers wrote:
>> These two patches are OK, please commit.
> 
> I created ChangeLog entries and committed both patches (one a few
> days ago, the second just now).  
> 
> Thank you, Maya!  If you have any further clean-ups, I'll be happy
> to help by committing them (once approved).
> 
>> (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>.)
> 
> I took this as a hint to further simplify ginclude/stddef.h. ;-)
> Thanks for pointing this out, Joseph!
> 
> Okay to apply the following?  Tested on x86_64-unknown-freebsd11.2.
> 
> Gerald
> 
> 2018-06-24  Gerald Pfeifer  <gerald@pfeifer.com>
> 
> 	* ginclude/stddef.h: Remove an obsolete comment on FreeBSD 5.
> 	Simplify logic for FreeBSD (twice).
OK.
jeff

      reply	other threads:[~2018-06-25 21:37 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
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 [this message]

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=0df801b7-6e2c-9be7-4510-da7c8d5e13f5@redhat.com \
    --to=law@redhat.com \
    --cc=andreast@FreeBSD.org \
    --cc=coypu@sdf.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=joseph@codesourcery.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).