From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [5999] Remove useless check_ops.sh
Date: Sat, 13 Dec 2008 09:03:29 +0000 [thread overview]
Message-ID: <E1LBQPJ-0004rT-JM@cvs.savannah.gnu.org> (raw)
Revision: 5999
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5999
Author: aurel32
Date: 2008-12-13 09:03:28 +0000 (Sat, 13 Dec 2008)
Log Message:
-----------
Remove useless check_ops.sh
Suggested by Stuart Brady.
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Removed Paths:
-------------
trunk/check_ops.sh
Deleted: trunk/check_ops.sh
===================================================================
--- trunk/check_ops.sh 2008-12-13 08:16:43 UTC (rev 5998)
+++ trunk/check_ops.sh 2008-12-13 09:03:28 UTC (rev 5999)
@@ -1,50 +0,0 @@
-#! /bin/sh
-# Script to check for duplicate function prologues in op.o
-# Typically this indicates missing FORCE_RET();
-# This script does not detect other errors that may be present.
-
-# Usage: check_ops.sh [-m machine] [op.o]
-# machine and op.o are guessed if not specified.
-
-if [ "x$1" = "x-m" ]; then
- machine=$2
- shift 2
-else
- machine=`uname -m`
-fi
-if [ -z "$1" ]; then
- for f in `find . -name op.o`; do
- /bin/sh "$0" -m $machine $f
- done
- exit 0
-fi
-
-case $machine in
- i?86)
- ret='\tret'
- ;;
- x86_64)
- ret='\tretq'
- ;;
- arm)
- ret='\tldm.*pc'
- ;;
- ppc* | powerpc*)
- ret='\tblr'
- ;;
- mips*)
- ret='\tjr.*ra'
- ;;
- s390*)
- ret='\tbr.*'
- ;;
- *)
- echo "Unknown machine `uname -m`"
- ;;
-esac
-echo $1
-# op_exit_tb causes false positives on some hosts.
-${CROSS}objdump -dr $1 | \
- sed -e '/>:$\|'"$ret"'/!d' -e 's/.*<\(.*\)>:/~\1:/' -e 's/.*'"$ret"'.*/!/' | \
- sed -e ':1;N;s/\n//;t1' | sed -e 's/~/\n/g' | grep -v '^op_exit_tb' | \
- grep '^op_.*!!'
reply other threads:[~2008-12-13 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1LBQPJ-0004rT-JM@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).