llvm-project.git/lldb/examples/python/disasm-stress-test.py, branch main

[lldb] fix(lldb/**.py): fix comparison to True/False (#94039)

2024-06-26T14:55:15+00:00

from PEP8
(https://peps.python.org/pep-0008/#programming-recommendations):

> Comparisons to singletons like None should always be done with is or
is not, never the equality operators.

Co-authored-by: Eisuke Kawashima

[NFC][Py Reformat] Reformat python files in lldb

2023-05-25T19:54:09+00:00

This is an ongoing series of commits that are reformatting our Python
code. Reformatting is done with `black` (23.1.0).

If you end up having problems merging this commit because you have made
changes to a python file, the best way to handle that is to run `git
checkout --ours ` and then reformat it with black.

RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential revision: https://reviews.llvm.org/D151460

Harmonize Python shebang

2020-07-16T19:53:45+00:00

Differential Revision: https://reviews.llvm.org/D83857

Python 2/3 compatibility: from future import print_function

2019-03-21T18:27:40+00:00

Differential Revision: https://reviews.llvm.org/D59580

llvm-svn: 356695

*** This commit represents a complete reformatting of the LLDB source code

2016-09-06T20:57:50+00:00

*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751

Added a --lldb option to override the location

2012-04-14T01:06:06+00:00

of LLDB.framework.

llvm-svn: 154728

The remaining time calculation didn't reflect the

2012-04-06T23:00:31+00:00

--start argument.  Fixed that.

llvm-svn: 154221

Removed a call to truncate() which slowed down

2012-04-06T21:04:20+00:00

the stress test by a LOT.

llvm-svn: 154208

Updated the disassembler stress tester with two

2012-04-06T20:53:23+00:00

new features:

(1) it outputs the instruction currently being
    tested to a log file, if a path is provided

(2) if instructed, it prints the time remaining
    in the exhaustive test

llvm-svn: 154205

Added a stress-tester for LLDB's disassembler.

2012-04-06T00:04:36+00:00

Right now it only works on Mac OS X, but other
platforms would just need to add their own
implementation of AddLLDBToSysPathOn*().

The stress-tester has two modes:

Used with --bytes N --random, the stress-tester
generates random instructions of length N and
runs them through the disassembler.  This is
suitable for architectures like Intel where it
is combinatorially infeasible to run through the
entire space of possible instructions.

Used with --bytes N and no arguments (or --start
S --stride T), the stress-tester tests the
disassembler with a monotonically increasing
sequence of instructions.

The --start and --stride arguments are intended
for use in multiprocessing environments.  Give
each core an ID from 0 .. T-1, pass the ID in as
the --start, and use T as the stride, and you
can launch one copy of the stress-tester on each
core you have available.

llvm-svn: 154143