aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2023-03-02 07:34:40 +1030
committerAlan Modra <amodra@gmail.com>2023-03-02 07:55:37 +1030
commit40e7bdbddc8ba144ae90641be58d6ac939ba096b (patch)
tree71eca4a86ea9e6ef614ec76145fc02a3b62c04df /gdb/python
parent9d834fcaa141705738d3322a753358f845dd8bbc (diff)
downloadbinutils-40e7bdbddc8ba144ae90641be58d6ac939ba096b.zip
binutils-40e7bdbddc8ba144ae90641be58d6ac939ba096b.tar.gz
binutils-40e7bdbddc8ba144ae90641be58d6ac939ba096b.tar.bz2
Using .mri in assembly
Changing mri mode between macro definition and use isn't good. This .macro x .endm .mri 1 x leads to a segfault. Fixed with the following patch, but I suppose what should really happen is that macros be marked as being mri mode when defined, and that determine whether the magic NARG parameter be supplied at expansion. Nobody has complained about this in 30 years so I'm not inclined to change gas behaviour to that extent. * macro.c (macro_expand): Don't segfault in mri mode if NARG formal isn't found.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions