mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-01-06 12:09:26 +08:00
76a4c1e063
This commit enables disassembler styling for AArch64. After this commit it is possible to have objdump style AArch64 disassembler output (using --disassembler-color option). Once the required GDB patches are merged, GDB will also style the disassembler output. The changes to support styling are mostly split between two files opcodes/aarch64-dis.c and opcodes/aarch64-opc.c. The entry point for the AArch64 disassembler can be found in aarch64-dis.c, this file handles printing the instruction mnemonics, and assembler directives (e.g. '.byte', '.word', etc). Some operands, mostly relating to assembler directives are also printed from this file. This commit changes all of this to pass through suitable styling information. However, for most "normal" instructions, the instruction operands are printed using a two step process. From aarch64-dis.c, in the print_operands function, the function aarch64_print_operand is called, this function is in aarch64-opc.c, and converts an instruction operand into a string. Then, back in print_operands (aarch64-dis.c), the operand string is printed. Unfortunately, the string returned by aarch64_print_operand can be quite complex, it will include syntax elements, like '[' and ']', in addition to register names and immediate values. In some cases, a single operand will expand into what will appear (to the user) as multiple operands separated with a ','. This makes the task of styling more complex, all these different components need to by styled differently, so we need to get the styling information out of aarch64_print_operand in some way. The solution that I propose here is similar to the solution that I used for the i386 disassembler. Currently, aarch64_print_operand uses snprintf to write the operand text into a buffer provided by the caller. What I propose is that we pass an extra argument to the aarch64_print_operand function, this argument will be a structure, the structure contains a callback function and some state. When aarch64_print_operand needs to format part of its output this can be done by using the callback function within the new structure, this callback returns a string with special embedded markers that indicate which mode should be used for each piece of text. Back in aarch64-dis.c we can spot these special style markers and use this to split the disassembler output up and apply the correct style to each piece. To make aarch64-opc.c clearer a series of new static functions have been added, e.g. 'style_reg', 'style_imm', etc. Each of these functions formats a piece of text in a different style, 'register' and 'immediate' in this case. Here's an example taken from aarch64-opc.c of the new functions in use: snprintf (buf, size, "[%s, %s]!", style_reg (styler, base), style_imm (styler, "#%d", opnd->addr.offset.imm)); The aarch64_print_operand function is also called from the assembler to aid in printing diagnostic messages. Right now I have no plans to add styling to the assembler output, and so, the callback function used in the assembler ignores the styling information and just returns an plain string. I've used the source files in gas/testsuite/gas/aarch64/ for testing, and have manually gone through and checked that the styling looks reasonable, however, I'm not an AArch64 expert, so it is possible that the odd piece is styled incorrectly. Please point out any mistakes I've made. With objdump disassembler color turned off, there should be no change in the output after this commit. |
||
---|---|---|
.. | ||
config | ||
doc | ||
po | ||
testsuite | ||
.gitignore | ||
acinclude.m4 | ||
aclocal.m4 | ||
app.c | ||
as.c | ||
as.h | ||
asintl.h | ||
atof-generic.c | ||
bignum.h | ||
bit_fix.h | ||
cgen.c | ||
cgen.h | ||
ChangeLog | ||
ChangeLog-0001 | ||
ChangeLog-0203 | ||
ChangeLog-2004 | ||
ChangeLog-2005 | ||
ChangeLog-2006 | ||
ChangeLog-2007 | ||
ChangeLog-2008 | ||
ChangeLog-2009 | ||
ChangeLog-2010 | ||
ChangeLog-2011 | ||
ChangeLog-2012 | ||
ChangeLog-2013 | ||
ChangeLog-2014 | ||
ChangeLog-2015 | ||
ChangeLog-2016 | ||
ChangeLog-2017 | ||
ChangeLog-2018 | ||
ChangeLog-2019 | ||
ChangeLog-2020 | ||
ChangeLog-9295 | ||
ChangeLog-9697 | ||
ChangeLog-9899 | ||
compress-debug.c | ||
compress-debug.h | ||
cond.c | ||
config.in | ||
configure | ||
configure.ac | ||
configure.com | ||
configure.tgt | ||
CONTRIBUTORS | ||
COPYING | ||
debug.c | ||
dep-in.sed | ||
depend.c | ||
dw2gencfi.c | ||
dw2gencfi.h | ||
dwarf2dbg.c | ||
dwarf2dbg.h | ||
ecoff.c | ||
ecoff.h | ||
ehopt.c | ||
emul-target.h | ||
emul.h | ||
expr.c | ||
expr.h | ||
flonum-copy.c | ||
flonum-konst.c | ||
flonum-mult.c | ||
flonum.h | ||
frags.c | ||
frags.h | ||
gdbinit.in | ||
hash.c | ||
hash.h | ||
input-file.c | ||
input-file.h | ||
input-scrub.c | ||
itbl-lex-wrapper.c | ||
itbl-lex.h | ||
itbl-lex.l | ||
itbl-ops.c | ||
itbl-ops.h | ||
itbl-parse.y | ||
listing.c | ||
listing.h | ||
literal.c | ||
macro.c | ||
macro.h | ||
MAINTAINERS | ||
Makefile.am | ||
Makefile.in | ||
makefile.vms | ||
messages.c | ||
NEWS | ||
obj.h | ||
output-file.c | ||
output-file.h | ||
read.c | ||
read.h | ||
README | ||
remap.c | ||
sb.c | ||
sb.h | ||
stabs.c | ||
subsegs.c | ||
subsegs.h | ||
symbols.c | ||
symbols.h | ||
tc.h | ||
write.c | ||
write.h |
README for GAS
A number of things have changed since version 1 and the wonderful
world of gas looks very different. There's still a lot of irrelevant
garbage lying around that will be cleaned up in time. Documentation
is scarce, as are logs of the changes made since the last gas release.
My apologies, and I'll try to get something useful.
Unpacking and Installation - Summary
====================================
See ../binutils/README.
To build just the assembler, make the target all-gas.
Documentation
=============
The GAS release includes texinfo source for its manual, which can be processed
into `info' or `dvi' forms.
The DVI form is suitable for printing or displaying; the commands for doing
this vary from system to system. On many systems, `lpr -d' will print a DVI
file. On others, you may need to run a program such as `dvips' to convert the
DVI file into a form your system can print.
If you wish to build the DVI file, you will need to have TeX installed on your
system. You can rebuild it by typing:
cd gas/doc
make as.dvi
The Info form is viewable with the GNU Emacs `info' subsystem, or the
stand-alone `info' program, available as part of the GNU Texinfo distribution.
To build the info files, you will need the `makeinfo' program. Type:
cd gas/doc
make info
Specifying names for hosts and targets
======================================
The specifications used for hosts and targets in the `configure'
script are based on a three-part naming scheme, but some short
predefined aliases are also supported. The full naming scheme encodes
three pieces of information in the following pattern:
ARCHITECTURE-VENDOR-OS
For example, you can use the alias `sun4' as a HOST argument or in a
`--target=TARGET' option. The equivalent full name is
`sparc-sun-sunos4'.
The `configure' script accompanying GAS does not provide any query
facility to list all supported host and target names or aliases.
`configure' calls the Bourne shell script `config.sub' to map
abbreviations to full names; you can read the script, if you wish, or
you can use it to test your guesses on abbreviations--for example:
% sh config.sub i386v
i386-unknown-sysv
% sh config.sub i786v
Invalid configuration `i786v': machine `i786v' not recognized
`configure' options
===================
Here is a summary of the `configure' options and arguments that are
most often useful for building GAS. `configure' also has several other
options not listed here.
configure [--help]
[--prefix=DIR]
[--srcdir=PATH]
[--host=HOST]
[--target=TARGET]
[--with-OPTION]
[--enable-OPTION]
You may introduce options with a single `-' rather than `--' if you
prefer; but you may abbreviate option names if you use `--'.
`--help'
Print a summary of the options to `configure', and exit.
`-prefix=DIR'
Configure the source to install programs and files under directory
`DIR'.
`--srcdir=PATH'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--host=HOST'
Configure GAS to run on the specified HOST. Normally the
configure script can figure this out automatically.
There is no convenient way to generate a list of all available
hosts.
`--target=TARGET'
Configure GAS for cross-assembling programs for the specified
TARGET. Without this option, GAS is configured to assemble .o files
that run on the same machine (HOST) as GAS itself.
There is no convenient way to generate a list of all available
targets.
`--enable-OPTION'
These flags tell the program or library being configured to
configure itself differently from the default for the specified
host/target combination. See below for a list of `--enable'
options recognized in the gas distribution.
`configure' accepts other options, for compatibility with configuring
other GNU tools recursively; but these are the only options that affect
GAS or its supporting libraries.
The `--enable' options recognized by software in the gas distribution are:
`--enable-targets=...'
This causes one or more specified configurations to be added to those for
which BFD support is compiled. Currently gas cannot use any format other
than its compiled-in default, so this option is not very useful.
`--enable-bfd-assembler'
This causes the assembler to use the new code being merged into it to use
BFD data structures internally, and use BFD for writing object files.
For most targets, this isn't supported yet. For most targets where it has
been done, it's already the default. So generally you won't need to use
this option.
Compiler Support Hacks
======================
On a few targets, the assembler has been modified to support a feature
that is potentially useful when assembling compiler output, but which
may confuse assembly language programmers. If assembler encounters a
.word pseudo-op of the form symbol1-symbol2 (the difference of two
symbols), and the difference of those two symbols will not fit in 16
bits, the assembler will create a branch around a long jump to
symbol1, and insert this into the output directly before the next
label: The .word will (instead of containing garbage, or giving an
error message) contain (the address of the long jump)-symbol2. This
allows the assembler to assemble jump tables that jump to locations
very far away into code that works properly. If the next label is
more than 32K away from the .word, you lose (silently); RMS claims
this will never happen. If the -K option is given, you will get a
warning message when this happens.
REPORTING BUGS IN GAS
=====================
Bugs in gas should be reported to:
https://sourceware.org/bugzilla/
See ../binutils/README for what we need in a bug report.
Copyright (C) 2012-2022 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.