public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "piotrdrag at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/15606] pl_PL: genitive month names support Date: Wed, 28 Oct 2015 21:04:00 -0000 [thread overview] Message-ID: <bug-15606-131-h4EoEVK3NS@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15606-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15606 Piotr Drąg <piotrdrag at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Piotr Drąg <piotrdrag at gmail dot com> --- I'm really excited and looking forward to your work. :) *** This bug has been marked as a duplicate of bug 10871 *** -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-30301-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed Oct 28 21:04:33 2015 Return-Path: <glibc-bugs-return-30301-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 73569 invoked by alias); 28 Oct 2015 21:04:33 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 73361 invoked by uid 48); 28 Oct 2015 21:04:29 -0000 From: "piotrdrag at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/10871] ru_RU: 'mon' array should contain both nominative and genitive cases Date: Wed, 28 Oct 2015 21:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: piotrdrag at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: libc-locales at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: <bug-10871-131-IuxjMJ6aDd@http.sourceware.org/bugzilla/> In-Reply-To: <bug-10871-131@http.sourceware.org/bugzilla/> References: <bug-10871-131@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00338.txt.bz2 Content-length: 268 https://sourceware.org/bugzilla/show_bug.cgi?id=10871 --- Comment #8 from Piotr Drąg <piotrdrag at gmail dot com> --- *** Bug 15606 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-30302-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed Oct 28 22:59:51 2015 Return-Path: <glibc-bugs-return-30302-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 99592 invoked by alias); 28 Oct 2015 22:59:51 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 99535 invoked by uid 55); 28 Oct 2015 22:59:47 -0000 From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/16068] [i386/x86_64] x86 and x86_64 fesetenv exclude state they should include Date: Wed, 28 Oct 2015 22:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.18 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: <bug-16068-131-DoZQWntg6V@http.sourceware.org/bugzilla/> In-Reply-To: <bug-16068-131@http.sourceware.org/bugzilla/> References: <bug-16068-131@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00339.txt.bz2 Content-length: 4986 https://sourceware.org/bugzilla/show_bug.cgi?id\x16068 --- Comment #3 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 2145f97cee01140d5369a8c67dc92eacfe8e4417 (commit) from 5878dd9d53a00fa28800236d79e38e55f85fc98d (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!45f97cee01140d5369a8c67dc92eacfe8e4417 commit 2145f97cee01140d5369a8c67dc92eacfe8e4417 Author: Joseph Myers <joseph@codesourcery.com> Date: Wed Oct 28 22:58:29 2015 +0000 Handle more state in i386/x86_64 fesetenv (bug 16068). fenv_t should include architecture-specific floating-point modes and status flags. i386 and x86_64 fesetenv limit which bits they use from the x87 status and control words, when using saved state, and limit which parts of the state they set to fixed values, when using FE_DFL_ENV / FE_NOMASK_ENV. The following should be included but are excluded in at least some cases: status and masking for the "denormal operand" exception (which isn't part of FE_ALL_EXCEPT); precision control (explicitly mentioned in Annex F as something that counts as part of the floating-point environment); MXCSR FZ and DAZ bits (for FE_DFL_ENV and FE_NOMASK_ENV). This patch arranges for this extra state to be handled by fesetenv (and thereby by feupdateenv, which calls fesetenv). (Note that glibc functions using floating point are not generally expected to work correctly with non-default values of this state, especially precision control, but it is still logically part of the floating-point environment and should be handled as such by fesetenv. Changes to the state relating to subnormals ought generally to work with libm functions when the arguments aren't subnormal and neither are the expected results; that's a consequence of functions avoiding spurious internal underflows.) A question arising from this is whether FE_NOMASK_ENV should or should not mask the "denormal operand" exception. I decided it should mask that exception. This is the status quo - previously that exception could only be unmasked by direct manipulation of control registers (possibly via <fpu_control.h>). In addition, it means that use of FE_NOMASK_ENV leaves a floating-point environment the same as could be obtained by fesetenv (FE_DFL_ENV); feenableexcept (FE_ALL_EXCEPT);, rather than an environment in which an exception is unmasked that could only be masked again by using fesetenv with FE_DFL_ENV (or a previously saved environment) - this exception not being usable with other <fenv.h> functions because it's outside FE_ALL_EXCEPT. Tested for x86_64 and x86. [BZ #16068] * sysdeps/i386/fpu/fesetenv.c: Include <fpu_control.h>. (FE_ALL_EXCEPT_X86): New macro. (__fesetenv): Use FE_ALL_EXCEPT_X86 in most places instead of FE_ALL_EXCEPT. Ensure precision control is included in floating-point state. Ensure that FE_DFL_ENV and FE_NOMASK_ENV handle "denormal operand exception" and clear FZ and DAZ bits. * sysdeps/x86_64/fpu/fesetenv.c: Include <fpu_control.h>. (FE_ALL_EXCEPT_X86): New macro. (__fesetenv): Use FE_ALL_EXCEPT_X86 in most places instead of FE_ALL_EXCEPT. Ensure precision control is included in floating-point state. Ensure that FE_DFL_ENV and FE_NOMASK_ENV handle "denormal operand exception" and clear FZ and DAZ bits. * sysdeps/x86/fpu/test-fenv-sse-2.c: New file. * sysdeps/x86/fpu/test-fenv-x87.c: Likewise. * sysdeps/x86/fpu/Makefile [$(subdir) = math] (tests): Add test-fenv-x87 and test-fenv-sse-2. [$(subdir) = math] (CFLAGS-test-fenv-sse-2.c): New variable. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 19 ++++ NEWS | 24 +++--- sysdeps/i386/fpu/fesetenv.c | 40 ++++++-- sysdeps/x86/fpu/Makefile | 3 +- sysdeps/x86/fpu/test-fenv-sse-2.c | 176 +++++++++++++++++++++++++++++++++++++ sysdeps/x86/fpu/test-fenv-x87.c | 169 +++++++++++++++++++++++++++++++++++ sysdeps/x86_64/fpu/fesetenv.c | 40 ++++++-- 7 files changed, 438 insertions(+), 33 deletions(-) create mode 100644 sysdeps/x86/fpu/test-fenv-sse-2.c create mode 100644 sysdeps/x86/fpu/test-fenv-x87.c -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2015-10-28 21:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-11 20:35 [Bug localedata/15606] New: " piotrdrag at gmail dot com 2014-06-13 15:09 ` [Bug localedata/15606] " fweimer at redhat dot com 2015-10-28 0:41 ` digitalfreak at lingonborough dot com 2015-10-28 21:04 ` piotrdrag at gmail dot com [this message]
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-15606-131-h4EoEVK3NS@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: linkBe 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).