public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] sys/_bitset.h: revert commit 74e014dbfab
Date: Fri, 24 Jun 2022 05:43:34 +0000 (GMT)	[thread overview]
Message-ID: <20220624054334.C6C793852745@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=3af17aef2b0391a9b58f03f7e37e14aed4f9cdfd

commit 3af17aef2b0391a9b58f03f7e37e14aed4f9cdfd
Author: Stefan Eßer <se@FreeBSD.org>
Date:   Tue Dec 7 23:34:33 2021 +0100

    sys/_bitset.h: revert commit 74e014dbfab
    
    It caused kernel build for PowerPC64 to fail.
    
    A different patch is being tested with make universe to make sure it
    works on all architectures.
    
    MFC after:      1 month<N [day[s]|week[s]|month[s]].  Request a reminder email>

Diff:
---
 newlib/libc/sys/rtems/include/sys/_bitset.h | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/newlib/libc/sys/rtems/include/sys/_bitset.h b/newlib/libc/sys/rtems/include/sys/_bitset.h
index 8ce632333..1c167daf3 100644
--- a/newlib/libc/sys/rtems/include/sys/_bitset.h
+++ b/newlib/libc/sys/rtems/include/sys/_bitset.h
@@ -61,13 +61,11 @@ struct _t {								\
  * Define a default type that can be used while manually specifying size
  * to every call.
  */
-__BITSET_DEFINE(__bitset, 1);
+__BITSET_DEFINE(bitset, 1);
 
 #if defined(_KERNEL) || defined(_WANT_FREEBSD_BITSET)
 #define	BITSET_DEFINE(_t, _s)	__BITSET_DEFINE(_t, _s)
 #define	BITSET_DEFINE_VAR(_t)	__BITSET_DEFINE_VAR(_t)
-
-#define	bitset			__bitset
 #endif
 
 #endif /* !_SYS__BITSET_H_ */


                 reply	other threads:[~2022-06-24  5:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220624054334.C6C793852745@sourceware.org \
    --to=sh@sourceware.org \
    --cc=newlib-cvs@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).