public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16642] [microblaze] __ASSUME_PSELECT incorrect
Date: Wed, 12 Mar 2014 17:30:00 -0000	[thread overview]
Message-ID: <bug-16642-131-g8IBbvrIjO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16642-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16642

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  abe6d90cc8c1c212dab7cde4468f9ed895d6ba86 (commit)
      from  dd3946c615184e1957a0cb09352cac72be5d6d5b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=abe6d90cc8c1c212dab7cde4468f9ed895d6ba86

commit abe6d90cc8c1c212dab7cde4468f9ed895d6ba86
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Mar 12 17:29:24 2014 +0000

    Fix __ASSUME_PSELECT for MicroBlaze (bug 16642).

    Reviewing (for all architectures, with a baseline kernel version of
    2.6.32) the kernel support for features for which __ASSUME_* macros
    would be affected by a move to 2.6.32 as minimum kernel version showed
    up that __ASSUME_PSELECT was wrongly defined for MicroBlaze, despite
    the corresponding syscall table entry not being wired up in the
    MicroBlaze kernel.

    This patch makes the MicroBlaze kernel-features.h undefine
    __ASSUME_PSELECT.  I'd also encourage wiring it up in the kernel (so
    you can then make this #undef conditional, and eventually obsolete
    once a recent-enough kernel is required).  I suspect it wasn't wired
    up because of the mistaken comment in asm/unistd.h "obsolete ->
    sys_pselect7" (there is no such syscall as pselect7).

        [BZ #16642]
        * sysdeps/unix/sysv/linux/microblaze/kernel-features.h
        (__ASSUME_PSELECT): Undefine.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                                          |    6 ++++++
 NEWS                                               |    4 ++--
 .../unix/sysv/linux/microblaze/kernel-features.h   |    3 +++
 3 files changed, 11 insertions(+), 2 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-03-12 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 18:26 [Bug libc/16642] New: " jsm28 at gcc dot gnu.org
2014-03-12 17:30 ` [Bug libc/16642] " jsm28 at gcc dot gnu.org
2014-03-12 17:30 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-13  6:43 ` fweimer at redhat dot com

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=bug-16642-131-g8IBbvrIjO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).