mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Άγγελος Οικονομόπουλος" <aoiko@cc.ece.ntua.gr>
To: Ian Wienand <ianw@gelato.unsw.edu.au>, Con Kolivas <conman@kolivas.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Cliff White <cliffw@osdl.org>
Subject: Re: [ANNOUNCE] contest benchmark v0.60
Date: Wed, 15 Jan 2003 14:08:13 +0200	[thread overview]
Message-ID: <200301151351.05419.aoiko@cc.ece.ntua.gr> (raw)
In-Reply-To: <20030115041524.GE21742@cse.unsw.edu.au>

On Wednesday 15 January 2003 06:15, Ian Wienand wrote:
> On Wed, Jan 15, 2003 at 02:16:48PM +1100, Con Kolivas wrote:
> > Ok some mildly annoying bugs have already shown up in this release.
> >
> > I've put up a contest-0.61pre on the contest website that addresses the
> > one which ruins the results and has some of the changes going into 0.61
>
> Con/Aggelos,
>
> What was the motivation for re-writing in C?

I gave up trying to make the script work in my desktop, which runs freebsd 
(too many little differences in the utilities used).

> I've done some hacking on the old version here, and so I realise that
> such a big shell script was getting a little out of hand, but surely
> perl or python is a better option for this application?

The script also had a few bugs that were actually artifacts of using bash 
(e.g. you had to use killall instead of just killing your children).

> If it's going to stay in C maybe we could integrate profiling support
> from /proc/profile, bypassing readprofile?  One of the guys here
> recently wanted to get profiling information from his program, and it
> would have been really good to have a library that could reset, start,
> pause and return in some format the profiling data.  If you think your
> users might be interested in profile outputs I can write something
> maybe we can both use.

Feel free to do so. I won't be able to help because
a) I'm not interested the feature :)
b) I don't have the time, I'm just helping Con squash most of the bugs in my 
code.

-- 
Follow each decision as closely as possible with its associated action.
            - The Elements of Programming Style (Kernighan & Plaugher)



  parent reply	other threads:[~2003-01-15 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 23:28 Con Kolivas
2003-01-15  3:16 ` Con Kolivas
2003-01-15  4:15   ` Ian Wienand
2003-01-15  4:39     ` Con Kolivas
2003-01-15  5:24       ` Ian Wienand
2003-01-15 19:28         ` Cliff White
2003-01-15 12:08     ` Άγγελος Οικονομόπουλος [this message]
2003-01-15 17:04     ` Cliff White

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=200301151351.05419.aoiko@cc.ece.ntua.gr \
    --to=aoiko@cc.ece.ntua.gr \
    --cc=cliffw@osdl.org \
    --cc=conman@kolivas.net \
    --cc=ianw@gelato.unsw.edu.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®