From: Matt Chapman <matthewc@cse.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: Re: making unwcheck.sh
Date: Sat, 15 Nov 2003 06:20:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106887730709091@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106883536806062@msgid-missing>
What's wrong with Perl? :) Okay, so there's plenty wrong with Perl, but
I think it's a decent tool for the job.
I wrote a quick Perl version, though it only works properly on 64-bit
platforms (reports an integer overflow otherwise). It wouldn't be too
hard to work around this if it's an issue (since for a given function
the upper 32 bits should presumably be invariant), in fact the same
workaround could probably be done in the awk script.
http://www.cse.unsw.edu.au/~matthewc/files/unwcheck.pl
Python seems to handle big numbers better but I don't really know enough
Python.
Matt
On Fri, Nov 14, 2003 at 10:38:39AM -0800, David Mosberger wrote:
> Is anybody willing/capable/interested in fixing unwcheck.sh so it can
> actually handle 64-bit addresses? I'm not much of an awk hacker but I
> noticed that the only reason the script works on the kernel is because
> it drops the first digit of each address (look for gsub() to see what
> I mean). Of course, that makes it work on the kernel, but it won't
> work for checking a shared object, for example. Perhaps the whole
> script should just be converted to a real[1] language?
>
>
> --david
>
> [1] real = anything other than awk, perl, or tcl... ;-)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-11-15 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 18:38 making unwcheck.sh David Mosberger
2003-11-15 6:20 ` Matt Chapman [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 23:33 David Mosberger
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=marc-linux-ia64-106887730709091@msgid-missing \
--to=matthewc@cse.unsw.edu.au \
--cc=linux-ia64@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