aboutsummaryrefslogtreecommitdiff
path: root/gdb/contrib/dwarf-to-dwarf-assembler.py
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2025-10-10 23:59:32 -0400
committerSimon Marchi <simon.marchi@efficios.com>2025-10-20 15:44:08 -0400
commita5cbe67512d3cfb1767733c8de74b70b45ebe052 (patch)
tree3cb8a7a4e5cf8635a14b22b444f4c85f62f7f7d0 /gdb/contrib/dwarf-to-dwarf-assembler.py
parentde49e8229b4d66beac71a8d7b6dd8e1cacc540c4 (diff)
downloadbinutils-a5cbe67512d3cfb1767733c8de74b70b45ebe052.zip
binutils-a5cbe67512d3cfb1767733c8de74b70b45ebe052.tar.gz
binutils-a5cbe67512d3cfb1767733c8de74b70b45ebe052.tar.bz2
gdb, gdbserver, gdbsupport: trim trailing whitespaces
I noticed my IDE (VSCode) starting to automatically trim trailing whitespaces on save, despite the setting for it being disabled. I realized that this is because the .editorconfig file now has trim_trailing_whitespace = true for many file types. If we have this EditorConfig setting forcing editors to trim trailing whitespaces, I think it would make sense to clean up trailing whitespaces from our files. Otherwise, people will always get spurious whitespace changes when editing these files. I did a mass cleanup using this command: $ find gdb gdbserver gdbsupport -type f \( \ -name "*.c" -o \ -name "*.h" -o \ -name "*.cc" -o \ -name "*.texi" -o \ -name "*.exp" -o \ -name "*.tcl" -o \ -name "*.py" -o \ -name "*.s" -o \ -name "*.S" -o \ -name "*.asm" -o \ -name "*.awk" -o \ -name "*.ac" -o \ -name "Makefile*" -o \ -name "*.sh" -o \ -name "*.adb" -o \ -name "*.ads" -o \ -name "*.d" -o \ -name "*.go" -o \ -name "*.F90" -o \ -name "*.f90" \ \) -exec sed -ri 's/[ \t]+$//' {} + I then did an autotools regen, because we don't actually want to change the Makefile and Makefile.in files that are generated. Change-Id: I6f91b83e3b8c4dc7d5d51a2ebf60706120efe691
Diffstat (limited to 'gdb/contrib/dwarf-to-dwarf-assembler.py')
0 files changed, 0 insertions, 0 deletions