Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Rich Felker
On Tue, Jun 11, 2013 at 04:13:53PM -0700, Roland McGrath wrote: > > Basically, top doesn't report correct CPU times. This is caused by > > sysconf() returning 100 while values read from /proc are true tick > > counts, hence 100 per second at most. > > In fact, that is not a "true tick count".

Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Roland McGrath
> Basically, top doesn't report correct CPU times. This is caused by > sysconf() returning 100 while values read from /proc are true tick > counts, hence 100 per second at most. In fact, that is not a "true tick count". Most modern Linux kernels have ticks at 1024Hz, for example. The ABI for

Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Richard Braun
On Tue, Jun 11, 2013 at 03:55:46PM -0700, Roland McGrath wrote: > > The /proc file system is merely an example. Also, it's not internal to > > libc, since it gets exported through sysconf(_SC_CLK_TCK). > > You'll have to explain what problem you think there is more thoroughly. Basically, top does

Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Roland McGrath
> The /proc file system is merely an example. Also, it's not internal to > libc, since it gets exported through sysconf(_SC_CLK_TCK). You'll have to explain what problem you think there is more thoroughly.

Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Richard Braun
On Tue, Jun 11, 2013 at 03:49:17PM -0700, Roland McGrath wrote: > This change doesn't make any sense to me. The explanation refers to /proc, > which is wholly irrelevant to libc internals. The /proc file system is merely an example. Also, it's not internal to libc, since it gets exported through

Re: [rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Roland McGrath
This change doesn't make any sense to me. The explanation refers to /proc, which is wholly irrelevant to libc internals.

[rbr...@sceen.net: [PATCH] Make __getclktck return 100 for the Hurd]

2013-06-11 Thread Richard Braun
- Forwarded message from Richard Braun - Date: Mon, 6 May 2013 21:49:56 +0200 From: Richard Braun To: bug-hurd@gnu.org Subject: [PATCH] Make __getclktck return 100 for the Hurd X-Mailer: git-send-email 1.7.2.5 While it's true that Mach time values are returned in microseconds, they are

Re: Hurd GSoC 2013 projects

2013-06-11 Thread Justus Winter
Quoting Justus Winter (2013-06-01 21:12:36) > > Copyright assignment. [...] > > Will do that. I did that, haven't heard anything yet. I'm not complaining, just stating facts. > > Weekly reports. > > Check. I setup a blog at https://teythoon.cryptobitch.de/ I read http://wiki.debian.org/Planet

Hurd port for GCC Go (was: [PATCH] gccgo patch 0-2 (9))

2013-06-11 Thread Thomas Schwinge
Hi! On Fri, 07 Jun 2013 11:14:31 +0200, Svante Signell wrote: > Attached are patches to enable gccgo to build properly on Debian > GNU/Hurd on gcc-4.7 (4.7.3-4). Thanks! I've begun integrating them into my GCC tree (based on upstream GCC trunk, so some changes to be done to your patches), and

setcontext et al. functions (was: Inquiry about GCC Summer Of Code project idea.)

2013-06-11 Thread Thomas Schwinge
Hi! On Wed, 15 May 2013 16:04:02 +0200, I wrote: > As for the roadblock: > > > On Tue, Apr 30, 2013 at 4:58 PM, Ian Lance Taylor wrote: > > > > > On Tue, Apr 30, 2013 at 6:53 AM, Thomas Schwinge > > > wrote: > > > > > > > > On I have ju