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] Revert "cpuset(9): Add CPU_FOREACH_IS(SET|CLR) and modify consumers to use it"
Date: Fri, 24 Jun 2022 05:42:59 +0000 (GMT)	[thread overview]
Message-ID: <20220624054259.96C1E3852760@sourceware.org> (raw)

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

commit 96ddb4055e747b5315c93f33a501d73703bb651a
Author: Mark Johnston <markj@FreeBSD.org>
Date:   Tue Sep 21 13:51:42 2021 -0400

    Revert "cpuset(9): Add CPU_FOREACH_IS(SET|CLR) and modify consumers to use it"
    
    This reverts commit 9068f6ea697b1b28ad1326a4c7a9ba86f08b985e.
    
    The underlying macro needs to be reworked to avoid problems with control
    flow statements.
    
    Reported by:    rlibby

Diff:
---
 newlib/libc/sys/rtems/include/sys/cpuset.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/newlib/libc/sys/rtems/include/sys/cpuset.h b/newlib/libc/sys/rtems/include/sys/cpuset.h
index 7779f0639..a321bddc2 100644
--- a/newlib/libc/sys/rtems/include/sys/cpuset.h
+++ b/newlib/libc/sys/rtems/include/sys/cpuset.h
@@ -62,8 +62,6 @@
 #define	CPU_COPY_STORE_REL(f, t)	BIT_COPY_STORE_REL(CPU_SETSIZE, f, t)
 #define	CPU_FFS(p)			BIT_FFS(CPU_SETSIZE, p)
 #define	CPU_FLS(p)			BIT_FLS(CPU_SETSIZE, p)
-#define	CPU_FOREACH_ISSET(i, p)		BIT_FOREACH_ISSET(CPU_SETSIZE, i, p)
-#define	CPU_FOREACH_ISCLR(i, p)		BIT_FOREACH_ISCLR(CPU_SETSIZE, i, p)
 #define	CPUSET_FSET			BITSET_FSET(_NCPUWORDS)
 #define	CPUSET_T_INITIALIZER		BITSET_T_INITIALIZER


                 reply	other threads:[~2022-06-24  5:42 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=20220624054259.96C1E3852760@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).