forked from Imagelibrary/binutils-gdb
[gdb/contrib] Add two rules in common-misspellings.txt
Eli mentioned [1] that given that we use US English spelling in our documentation, we should use "behavior" instead of "behaviour". In wikipedia-common-misspellings.txt there's a rule: ... behavour->behavior, behaviour ... which leaves this as a choice. Add an overriding rule to hardcode the choice to common-misspellings.txt: ... behavour->behavior ... and add a rule to rewrite behaviour into behavior: ... behaviour->behavior ... and re-run spellcheck.sh on gdb*. Tested on x86_64-linux. [1] https://sourceware.org/pipermail/gdb-patches/2024-November/213371.html
This commit is contained in:
@@ -4401,7 +4401,7 @@ cross_ref (int fd, union aux_ext *ax, struct type **tpp,
|
||||
case btTypedef:
|
||||
/* Follow a forward typedef. This might recursively
|
||||
call cross_ref till we get a non typedef'ed type.
|
||||
FIXME: This is not correct behaviour, but gdb currently
|
||||
FIXME: This is not correct behavior, but gdb currently
|
||||
cannot handle typedefs without type copying. Type
|
||||
copying is impossible as we might have mutual forward
|
||||
references between two files and the copied type would not
|
||||
@@ -4427,7 +4427,7 @@ cross_ref (int fd, union aux_ext *ax, struct type **tpp,
|
||||
{
|
||||
/* Parse the type for a normal typedef. This might recursively call
|
||||
cross_ref till we get a non typedef'ed type.
|
||||
FIXME: This is not correct behaviour, but gdb currently
|
||||
FIXME: This is not correct behavior, but gdb currently
|
||||
cannot handle typedefs without type copying. But type copying is
|
||||
impossible as we might have mutual forward references between
|
||||
two files and the copied type would not get filled in when
|
||||
|
||||
Reference in New Issue
Block a user