public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17263] New: [powerpc] __get_clockfreq broken for 32-bit non-power4 glibc Date: Tue, 12 Aug 2014 21:29:00 -0000 [thread overview] Message-ID: <bug-17263-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17263 Bug ID: 17263 Summary: [powerpc] __get_clockfreq broken for 32-bit non-power4 glibc Product: glibc Version: 2.19 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jsm28 at gcc dot gnu.org CC: drepper.fsp at gmail dot com Host: powerpc*-*-* sysdeps/unix/sysv/linux/powerpc/get_clockfreq.c uses the VDSO to get an hp_timing_t result. The VDSO always provides a 64-bit result, but hp_timing_t is 32-bit if the power4 sysdeps directories aren't used, resulting in only r3 (the high part of the result, = 0) being used, a value of 0 being returned and test-gettimebasefreq failing. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-08-12 21:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-12 21:29 jsm28 at gcc dot gnu.org [this message] 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
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@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).