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 stdio/17522] `fputws' errors out when writing wide characters to unbuffered stream
Date: Tue, 16 Dec 2014 11:26:00 -0000	[thread overview]
Message-ID: <bug-17522-131-Ri2FNoJUqn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17522-131@http.sourceware.org/bugzilla/>

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

--- Comment #9 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  a0d424ef9d7fc34f7d1a516f38c8efb1e8692a03 (commit)
       via  8b460906cdb8ef1501fa5dcff54206b201e527d5 (commit)
       via  fa13e15b9a5cc49c9c6dee33084c3ff54d48e50e (commit)
       via  0e426475a70800b6a17daa7a8ebbafeabfcbc022 (commit)
      from  4f646bce1cae4031bfe7517e4793f1edc1a15220 (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=a0d424ef9d7fc34f7d1a516f38c8efb1e8692a03

commit a0d424ef9d7fc34f7d1a516f38c8efb1e8692a03
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Tue Dec 16 16:53:05 2014 +0530

    Fix 'array subscript is above array bounds' warning in res_send.c

    I see this warning in my build on F21 x86_64, which seems to be due to
    a weak check for array bounds.  Fixed by making the bounds check
    stronger.

    This is not an actual bug since nscount is never set to anything
    greater than MAXNS.  The compiler however does not know this, so we
    need the stronger bounds check to quieten the compiler.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8b460906cdb8ef1501fa5dcff54206b201e527d5

commit 8b460906cdb8ef1501fa5dcff54206b201e527d5
Author: Arjun Shankar <arjun.is@lostca.se>
Date:   Tue Dec 16 15:21:01 2014 +0530

    Modify libio/tst-fopenloc.c to use test-skeleton.c

    This test would earlier fail when run under test-skeleton.c due to
    bug #17522 in 'fputws'. That bug is now fixed and so this test may
    be modified.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fa13e15b9a5cc49c9c6dee33084c3ff54d48e50e

commit fa13e15b9a5cc49c9c6dee33084c3ff54d48e50e
Author: Arjun Shankar <arjun.is@lostca.se>
Date:   Tue Dec 16 15:19:51 2014 +0530

    Modify stdlib/tst-bsearch.c to use test-skeleton.c

    This test used to define a 'struct entry' that conflicts with the
    definition in search.h included in test-skeleton. The struct is
    now renamed 'item'.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0e426475a70800b6a17daa7a8ebbafeabfcbc022

commit 0e426475a70800b6a17daa7a8ebbafeabfcbc022
Author: Arjun Shankar <arjun.is@lostca.se>
Date:   Tue Dec 16 15:18:46 2014 +0530

    Modify stdio-common/tst-fseek.c to use test-skeleton.c

    This test needs a TIMEOUT longer than the default 2 seconds since it
    sleeps twice for a second each.

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

Summary of changes:
 ChangeLog                |   15 +++++++++++++++
 libio/tst-fopenloc.c     |    7 +++++--
 resolv/res_send.c        |    2 +-
 stdio-common/tst-fseek.c |    8 ++++++--
 stdlib/tst-bsearch.c     |   27 +++++++++++++++------------
 5 files changed, 42 insertions(+), 17 deletions(-)

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


  parent reply	other threads:[~2014-12-16 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 15:57 [Bug stdio/17522] New: " arjun.is at lostca dot se
2014-10-29 18:03 ` [Bug stdio/17522] " carlos at redhat dot com
2014-10-29 18:43 ` arjun.is at lostca dot se
2014-10-29 18:49 ` carlos at redhat dot com
2014-10-29 19:12 ` arjun.is at lostca dot se
2014-10-29 19:16 ` carlos at redhat dot com
2014-11-03  9:00 ` cvs-commit at gcc dot gnu.org
2014-11-03  9:03 ` schwab@linux-m68k.org
2014-12-16 11:26 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-20 15: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-17522-131-Ri2FNoJUqn@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).