public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Justin Cormack <justin@specialbusservice.com>
To: libc-ports@sourceware.org
Subject: __unused changes
Date: Mon, 25 Nov 2013 10:26:00 -0000	[thread overview]
Message-ID: <CAK4o1WyNFCKg8Qo2Fn5eOTxBx7zmX4-Gc8UPWKT81yJBqvkgcQ@mail.gmail.com> (raw)

Hello,

I recently proposed a change in glibc, across all architectures, to
change the use of __unused for unused struct members to
__glibc_reserved.

You can see the thread here
http://sourceware-org.1504.n7.nabble.com/Re-PATCH-Use-unused0-instead-of-unused-for-user-visible-struct-members-td248849.html

The reason behind this is that historically BSD software has used
__unused as a macro for __attribute__ ((__unused__)) and this has
caused compilation issues when using this code with glibc.

This should not cause any breakage, as these struct members are not
supposed to be used publicly, but please look for any unintended
breakage that could arise.

Thanks

Justin

                 reply	other threads:[~2013-11-25  9:14 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=CAK4o1WyNFCKg8Qo2Fn5eOTxBx7zmX4-Gc8UPWKT81yJBqvkgcQ@mail.gmail.com \
    --to=justin@specialbusservice.com \
    --cc=libc-ports@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).