[Bug libc/9894] New: Support for PI futexes wrongly marked as introduced in 2.6.18

[Bug libc/9894] New: Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

While support for PI futexes has been added in 2.6.18, it depends on
futex_atomic_cmpxchg_inatomic() being implemented, which has been
implemented later (or not yet implemented) on some architectures.

Below is the kernel version where the support has been added for main
and ports glibc architectures;

- i386:    2.6.18
- ia64:    2.6.19
- powerpc: 2.6.18
- s390:    2.6.18
- sparc:   not implemented
- sparc64: 2.6.18
- sh:      2.6.23
- x86_64:  2.6.18

- alpha:   not implemented
- arm:     2.6.28
- cris:    not implemented
- hppa :   2.6.19
- m68k:    not implemented
- mips:    2.6.18

Patches to fix the problem are following soon

-- 
           Summary: Support for PI futexes wrongly marked as introduced in
                    2.6.18
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: aurelien at aurel32 dot net
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-24 23:20 -------
Created an attachment (id=3764)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3764&action=view)
patch for main architecture


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-24 23:21 -------
Created an attachment (id=3767)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3767&action=view)
patch for hppa


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-24 23:20 -------
Created an attachment (id=3765)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3765&action=view)
patch for arm


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-24 23:21 -------
Created an attachment (id=3766)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3766&action=view)
patch for mips


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-27 15:07 -------
The same problem also exists with robust mutexes and is due to the same problem,
ie they are available when both get/set_robust_list syscalls have been added
*and* futex_atomic_cmpxchg_inatomic() is available. This give the following
availabilities for main
and ports glibc architectures:

- i386:    2.6.17
- ia64:    2.6.19
- powerpc: 2.6.17
- s390:    2.6.18
- sparc:   not implemented
- sparc64: 2.6.19
- sh:      2.6.23
- x86_64:  2.6.17

- alpha:   not implemented
- arm:     2.6.28
- cris:    not implemented
- hppa :   2.6.19
- m68k:    not implemented
- mips:    2.6.19

Update patches fixing the problem will follow.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-27 15:08 -------
Created an attachment (id=3777)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3777&action=view)
Updated patch for main architectures


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #3764 is|0                           |1
           obsolete|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-27 15:09 -------
Created an attachment (id=3780)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3780&action=view)
Updated patch for mips


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #3766 is|0                           |1
           obsolete|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-27 15:09 -------
Created an attachment (id=3779)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3779&action=view)
Updated patch for hppa


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #3767 is|0                           |1
           obsolete|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-02-27 15:08 -------
Created an attachment (id=3778)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3778&action=view)
Updated patch for arm


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #3765 is|0                           |1
           obsolete|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[jsm28 at gcc dot gnu dot org]

------- Additional Comments From jsm28 at gcc dot gnu dot org  2009-04-15 20:47 -------
The ARM and MIPS changes look OK; I haven't applied them because they
depend on the libc changes.  It might be useful to do a version of the ports
changes that works with present libc (so conditionally #undefing the macros
after including the libc kernel-features.h), which could be reverted and
replaced with the present patch versions after the libc changes go in.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[aurelien at aurel32 dot net]

------- Additional Comments From aurelien at aurel32 dot net  2009-05-01 10:56 -------
I fully agree that we can do a ports specific patch until the other patch is 
applied to libc. However it would be a lot easier to apply the libc patch 
first. 

What is the problem with the current libc patch? It is not specific to ports as 
it also concerns two main architectures from libc, that is sparc and sh.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9894

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[jsm28 at gcc dot gnu.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=9894

--- Comment #12 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-19 02:19:53 UTC ---
Could you update the patches for current sources (taking account of ia64 no
longer being included) and for any implementations for additional architectures
in the mean time?  (Patches for any additional ports architectures are
optional, but the libc patch needs updating.)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[jsm28 at gcc dot gnu.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=9894

--- Comment #13 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-08-03 14:11:51 UTC ---
Aurelien, ping regarding updating the patches for current sources and kernels. 
You mentioned that you were trying to review kernel-features.h generally - but
incremental patches that actually exist, updating things only for some macros
or some architectures, are better than ideal complete patches that don't exist
- try to send small pieces to libc-alpha (CC libc-ports where ports
kernel-features.h headers are updated as well) each of which fixes some
particular problem without making things worse in any case.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[schwab@linux-m68k.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=9894

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|drepper.fsp at gmail dot    |unassigned at sourceware
                   |com                         |dot org

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[neleai at seznam dot cz]

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

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |neleai at seznam dot cz

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[cvs-commit at gcc dot gnu.org]

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

--- Comment #15 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  47c5adebd2c864a098c3af66e61e1147dc3cf0b4 (commit)
      from  d7a68734f7bbc76586017461cff19af0d9cb4df8 (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=47c5adebd2c864a098c3af66e61e1147dc3cf0b4

commit 47c5adebd2c864a098c3af66e61e1147dc3cf0b4
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Mon Mar 31 12:55:18 2014 +0000

    Correct robust mutex / PI futex kernel assumptions (bug 9894).

    This patch continues fixing __ASSUME_* issues in preparation for
    moving to a 2.6.32 minimum kernel version by addressing assumptions on
    robust mutex and PI futex support availability.  Those assumptions are
    bug 9894, but to be clear this patch does not address all the issues
    from that bug about wrong version assumptions, only those still
    applicable for --enable-kernel=2.6.32 or later (with the expectation
    that the move to that minimum kernel will obsolete the other parts of
    the bug).  The patch is independent of
    <https://sourceware.org/ml/libc-alpha/2014-03/msg00585.html>, my other
    pending-review patch preparing for the kernel version change; the two
    together complete all the changes I believe are needed in preparation
    regarding any macro in sysdeps/unix/sysv/linux/kernel-features.h that
    would be affected by such a change.  (I have not checked the
    correctness of macros whose conditions are unaffected by such a
    change, or macros only defined in other kernel-features.h files.)

    As discussed in that bug, robust mutexes and PI futexes need
    futex_atomic_cmpxchg_inatomic to be implemented, in addition to
    certain syscalls needed for robust mutexes (and
    architecture-independent kernel pieces for all the features in
    question).  That is, as I understand it, they need
    futex_atomic_cmpxchg_inatomic to *work* (not return an ENOSYS error).

    The issues identified in my analysis relate to ARM, M68K, MicroBlaze,
    MIPS and SPARC.

    On ARM, whether futex_atomic_cmpxchg_inatomic works depends on the
    kernel configuration.  As of 3.13, the condition for *not* working is
    CONFIG_CPU_USE_DOMAINS && CONFIG_SMP.  As of 2.6.32 it was simply
    CONFIG_SMP that meant the feature was not implemented.  I don't know
    if there are any circumstances in which we can say "we can assume a
    userspace glibc binary built with these options will never run on a
    kernel with the problematic configuration", but at least for now I'm
    just undefining the relevant __ASSUME_* macros for ARM.

    On M68K, two of the three macros are undefined for kernels before
    3.10, but as far as I can see __ASSUME_FUTEX_LOCK_PI is in the same
    group needing futex_atomic_cmpxchg_inatomic support and so should be
    undefined as well.

    On MicroBlaze the required support was added in 2.6.33.

    On MIPS, the support depends on cpu_has_llsc in the kernel - that is,
    actual hardware LL/SC support (GCC and glibc for MIPS GNU/Linux rely
    on the instructions being supported in some way, but it may be kernel
    emulation; futex_atomic_cmpxchg_inatomic doesn't work with that
    emulation).  The same condition as in GCC for indicating LL/SC support
    may not be available is used for undefining the macros in glibc,
    __mips == 1 || defined _MIPS_ARCH_R5900.  (Maybe we could in fact
    desupport MIPS processors without the hardware support in glibc.)

    On SPARC, 32-bit kernels don't support futex_atomic_cmpxchg_inatomic;
    __arch64__ || __sparc_v9__ is used as the condition for binaries that
    won't run on 32-bit kernels.

    This patch is not tested beyond the sanity check of an x86_64 build.

        [BZ #9894]
        * sysdeps/unix/sysv/linux/kernel-features.h
        [__sparc__ && !__arch64__ && !__sparc_v9__]
        (__ASSUME_SET_ROBUST_LIST): Do not define.
        [__sparc__ && !__arch64__ && !__sparc_v9__]
        (__ASSUME_FUTEX_LOCK_PI): Likewise.
        [__sparc__ && !__arch64__ && !__sparc_v9__] (__ASSUME_REQUEUE_PI):
        Likewise.
        * sysdeps/unix/sysv/linux/arm/kernel-features.h
        (__ASSUME_FUTEX_LOCK_PI): Undefine.
        (__ASSUME_REQUEUE_PI): Likewise.
        (__ASSUME_SET_ROBUST_LIST): Likewise.
        * sysdeps/unix/sysv/linux/m68k/kernel-features.h
        [__LINUX_KERNEL_VERSION < 0x030a00] (__ASSUME_FUTEX_LOCK_PI):
        Undefine.
        * sysdeps/unix/sysv/linux/microblaze/kernel-features.h
        [__LINUX_KERNEL_VERSION < 0x020621] (__ASSUME_FUTEX_LOCK_PI):
        Likewise.
        [__LINUX_KERNEL_VERSION < 0x020621] (__ASSUME_REQUEUE_PI):
        Likewise.
        [__LINUX_KERNEL_VERSION < 0x020621] (__ASSUME_SET_ROBUST_LIST):
        Likewise.
        * sysdeps/unix/sysv/linux/mips/kernel-features.h
        [__mips == 1 || _MIPS_ARCH_R5900] (__ASSUME_FUTEX_LOCK_PI):
        Undefine.
        [__mips == 1 || _MIPS_ARCH_R5900] (__ASSUME_REQUEUE_PI): Likewise.
        [__mips == 1 || _MIPS_ARCH_R5900] (__ASSUME_SET_ROBUST_LIST):
        Likewise.

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

Summary of changes:
 ChangeLog                                          |   29 ++++++++++++++++++++
 sysdeps/unix/sysv/linux/arm/kernel-features.h      |    7 +++++
 sysdeps/unix/sysv/linux/kernel-features.h          |   20 +++++++++----
 sysdeps/unix/sysv/linux/m68k/kernel-features.h     |    1 +
 .../unix/sysv/linux/microblaze/kernel-features.h   |    7 +++++
 sysdeps/unix/sysv/linux/mips/kernel-features.h     |    8 +++++
 6 files changed, 66 insertions(+), 6 deletions(-)

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[cvs-commit at gcc dot gnu.org]

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

--- Comment #16 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  d0f5b3f851cfced84e3228977eb8dfdc9c607231 (commit)
      from  9a461d467f56a16e199d4c23d3e327eb886035af (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=d0f5b3f851cfced84e3228977eb8dfdc9c607231

commit d0f5b3f851cfced84e3228977eb8dfdc9c607231
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Apr 30 15:39:30 2014 +0000

    Increase minimum Linux kernel version to 2.6.32.

    This patch increases the minimum Linux kernel version for glibc to
    2.6.32, as discussed in the thread starting at
    <https://sourceware.org/ml/libc-alpha/2014-01/msg00511.html>.

    This patch just does the minimal change to arch_minimum_kernel
    settings (and LIBC_LINUX_VERSION, which determines the minimum kernel
    headers version, as it doesn't make sense for that to be older than
    the minimum kernel that can be used at runtime).  Followups would be
    expected to do, roughly and not necessarily precisely in this order:

    * Remove __LINUX_KERNEL_VERSION checks in kernel-features.h files
      where those checks are always true / always false for kernels 2.6.32
      and above.

    * Otherwise simplify/improve conditionals in those files (for example,
      where defining once in the main file then undefining in
      architecture-specific files makes things clearer than having lots of
      separate definitions of the same macro), possibly fixing in the
      process cases where a macro should optimally have been defined for a
      given architecture but wasn't.  (In the review in preparation for
      this version increase I checked what the right conditions should be
      for all macros in the main kernel-features.h whose definitions there
      would have been affected by the increase - but I only fixed that
      subset of the issues found where --enable-kernel=2.6.32 would have
      caused a kernel feature to be wrongly assumed to be present, not any
      cases where a feature is not assumed but could be assumed.)

    * Remove conditionals on __ASSUME_* where they can now be taken to be
      always-true, and the definitions when the macros are only used in
      Linux-specific files.

    * Split more architectures out of the main kernel-features.h (like
      ex-ports architectures), once various of the architecture
      conditionals there have been eliminated so the new
      architecture-specific files are no larger than actually necessary.

    Tested x86_64.

    2014-03-27  Joseph Myers  <joseph@codesourcery.com>

        [BZ #9894]
        * sysdeps/unix/sysv/linux/configure.ac (LIBC_LINUX_VERSION):
        Change to 2.6.32.
        (arch_minimum_kernel): Change all 2.6.16 settings to 2.6.32.
        * sysdeps/unix/sysv/linux/configure: Regenerated.
        * sysdeps/unix/sysv/linux/microblaze/configure.ac: Remove file.
        * sysdeps/unix/sysv/linux/microblaze/configure: Likewise.
        * sysdeps/unix/sysv/linux/tile/configure.ac: Likewise.
        * sysdeps/unix/sysv/linux/tile/configure: Likewise.
        * README: Update reference to required Linux kernel version.
        * manual/install.texi (Linux): Update reference to required Linux
        kernel headers version.
        * INSTALL: Regenerated.

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

Summary of changes:
 ChangeLog                                       |   14 +++++++++
 INSTALL                                         |    2 +-
 NEWS                                            |    5 +++-
 README                                          |    2 +-
 manual/install.texi                             |    2 +-
 sysdeps/unix/sysv/linux/configure               |   34 +++++++++++-----------
 sysdeps/unix/sysv/linux/configure.ac            |   18 ++++++------
 sysdeps/unix/sysv/linux/microblaze/configure    |    4 ---
 sysdeps/unix/sysv/linux/microblaze/configure.ac |    4 ---
 sysdeps/unix/sysv/linux/tile/configure          |    4 ---
 sysdeps/unix/sysv/linux/tile/configure.ac       |    4 ---
 11 files changed, 47 insertions(+), 46 deletions(-)
 delete mode 100644 sysdeps/unix/sysv/linux/microblaze/configure
 delete mode 100644 sysdeps/unix/sysv/linux/microblaze/configure.ac
 delete mode 100644 sysdeps/unix/sysv/linux/tile/configure
 delete mode 100644 sysdeps/unix/sysv/linux/tile/configure.ac

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[jsm28 at gcc dot gnu.org]

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED

--- Comment #17 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
Fixed for 2.20.

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[fweimer at redhat dot com]

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[mkl at pengutronix dot de]

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

Marc Kleine-Budde <mkl at pengutronix dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |mkl at pengutronix dot de
         Resolution|FIXED                       |---

--- Comment #19 from Marc Kleine-Budde <mkl at pengutronix dot de> ---
(In reply to Joseph Myers from comment #17)
> Fixed for 2.20.

Commit:

    47c5adebd2c8 Correct robust mutex / PI futex kernel assumptions (bug 9894).

Causes a regression on ARM, see Bug 18463.

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

Marc

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

[Bug libc/9894] Support for PI futexes wrongly marked as introduced in 2.6.18

[jsm28 at gcc dot gnu.org]

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #20 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
This bug is fixed.  Do not try to modify the scope of an existing bug to cover
things not in the accepted scope at the time it was fixed.

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