aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2024-07-19 11:54:09 +0200
committerJan Beulich <jbeulich@suse.com>2024-07-19 11:54:09 +0200
commit0d96d156aca0aa022f174be4add3d3cb56d7f6b7 (patch)
treeea3e58d79d83bd525bcb964bda2e900a1614d92f /gdb
parentda0fa10a4e0967be13cfa86a64a992602161b31d (diff)
downloadbinutils-0d96d156aca0aa022f174be4add3d3cb56d7f6b7.zip
binutils-0d96d156aca0aa022f174be4add3d3cb56d7f6b7.tar.gz
binutils-0d96d156aca0aa022f174be4add3d3cb56d7f6b7.tar.bz2
gas: consistently drop trailing whitespace when scrubbing
From especially the checks for the two separator forms it appears to follow that the construct being touched is about trailing whitespace. In such a case, considering that for many targets ordinary and line comment chars overlap, take into account that line comment chars override ordinary ones in lex[] (logic elsewhere in do_scrub_chars() actually depends on that ordering, and also accounts for this overriding). Plus of course IS_NEWLINE() would better also be consulted. Note also that the DOUBLESLASH_LINE_COMMENTS change should generally have no effect just yet; it's a prereq for a later change but better fits here. Leave respective comments as well, and update documentation to correct which comment form is actually replaced by a single blank (i.e. neither the ones starting with what {,tc_}comment_chars[] has nor the ones starting with what line_comment_chars[] has).
Diffstat (limited to 'gdb')
0 files changed, 0 insertions, 0 deletions