Because referencing the bible is not the best idea. It would be best to
not duplicate stuff around, so:
* The base-library is a minimal, never-evolving set of files
* The community documentation is in the fxdoc repository
* The OS files are on the bible's common/ folder (cleaning needed)
New features:
* The syscall pass now resolves syscalls for the input target, provided
that an OS is mapped on the ROM region.
* Formalized the variations of print's arguments as a sequence (tree, to
be precise) of /promotions/.
* Added a short notion of Symbol and SymbolTable, and a loader for them.
Data files of type "symbol" are read as such and provide name to
syscalls or arbitrary addresses.
Code changes:
* The disassembly operation of the command-line interface is now finally
in its own file with more room.
* Encoded the tree structure of promotions as a sequence of (mainly
tail-calling) inter-calling methods in the print pass.
-> The cfg pass loads the function into memory, annotates leaders and
jumps, and resolves delay slots.
-> The pcrel pass currently computes locations for pc-relative moves and
jumps, but does not yet compute the pc-relative moved data.
-> The print pass displays the results of analysis with various layout
and formatting options.
-> The Library class handles the loading and parsing of data files. This
is because any fxos application will use this since everyone will
have only one library.
-> Add a logging function that automatically format()s everything in
sight with basic logging levels and a verbose mode. Standard logs are
prefixed with __func__ for debugging purposes.
-> Allow format() to take std::string arguments for %s by statically
extracting c_str()s.
-> Add a simple timing utility to understand which file load or
disassembler pass takes up the time.
* Separate OS and Target conceptually; now an OS is created on an
existing target which must have ROM bound.
* Add a configuration file with a data library and description files
which are automatically loaded at startup.
* As a first application, implement target descriptions. It is now
possible (given the proper library) to type [fxos info fx@3.10] to get
information on the fx OS version 3.10.
* Set up the pass infrastructure and the first few easy passes. This
is still a Work In Progress and not yet called from the command-line.
* Improve the copy/move behavior of classes (C++ concerns).
* Add instruction metadata, which will make it easier to write actual
useful analysis passes.
* switch from File to Buffer to manage file contents
* boilerplate for a proprer command-line interface, and complete help
* add a notion of Addressable to avoid losing the source address of very
information provided by the OS type
* use addressables in the AbstractMemory interface
* fully parse the header and footer of OSes
* bring [fxos info] to the level of the previous implementation
* make most of the OS attributes public
* use char* instead of void* for translation, since void* arithmetic
triggers a hell of warnings in C++
Contains basic stuff to start working:
* Loading files and assembly instruction descriptions
* Create a 64k-entry assembly decoding table
* Standard memory regions and information
* Create targets where files can be mapped at any addresses
* Load OSes and detect a few basic things
Lephenixnoir