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/17263] [powerpc] __get_clockfreq broken for 32-bit non-power4 glibc
Date: Wed, 13 Aug 2014 16:07:00 -0000	[thread overview]
Message-ID: <bug-17263-131-0A7iorLIJp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17263-131@http.sourceware.org/bugzilla/>

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

--- 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  d44a052c499a3e2908862cff28cdb85d8aec246f (commit)
      from  e44c8b0eb7339787fbc6b1d4a2d1bd5046bc103f (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=d44a052c499a3e2908862cff28cdb85d8aec246f

commit d44a052c499a3e2908862cff28cdb85d8aec246f
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Aug 13 16:06:18 2014 +0000

    Fix powerpc32 __get_clockfreq for non-power4 (bug 17263).

    In my powerpc32 testing I've observed misc/test-gettimebasefreq
    failing.

    This is a glibc build (soft-float, though that's not relevant here)
    without any --with-cpu and without any special configuration of the
    default CPU for GCC either.  In particular, it's one not using
    sysdeps/powerpc/powerpc32/power4/hp-timing.h (although in fact the
    processor I'm using for testing is POWER4-based), so hp_timing_t is
    32-bit not 64-bit.  But the VDSO call being used by
    INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK is generating a 64-bit result
    (high part in r3, low part in r4).  The code extracting that result,
    however, expects a result of the type hp_timing_t as passed to
    INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK, meaning that only r3 (= 0) is
    used and the value in r4 is ignored.  This patch fixes this by always
    using uint64_t as the type in INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK -
    reflecting the actual ABI (unconditional in the kernel) of that VDSO
    call.  This is the minimal change for this issue - no check for
    overflow, no change of the type of the timebase_freq variable or the
    return type of __get_clockfreq to something other than hp_timing_t
    (such a change would simply move the implicit conversions to the over
    callers of that function), no change to hp_timing_t itself.

    Tested for powerpc32 soft float.

        [BZ #17263]
        * sysdeps/unix/sysv/linux/powerpc/get_clockfreq.c: Include
        <stdint.h>.
        (__get_clockfreq): Use uint64_t instead of hp_timing_t in
        INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK call.

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

Summary of changes:
 ChangeLog                                       |    8 ++++++++
 NEWS                                            |    2 +-
 sysdeps/unix/sysv/linux/powerpc/get_clockfreq.c |    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-08-13 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 21:29 [Bug libc/17263] New: " jsm28 at gcc dot gnu.org
2014-08-13 16:07 ` [Bug libc/17263] " jsm28 at gcc dot gnu.org
2014-08-13 16:07 ` cvs-commit at gcc dot gnu.org [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-17263-131-0A7iorLIJp@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).