aboutsummaryrefslogtreecommitdiff
path: root/contrib/check-params-in-docs.py
diff options
context:
space:
mode:
authorIain Sandoe <iain@sandoe.co.uk>2023-11-23 09:44:55 +0000
committerIain Sandoe <iain@sandoe.co.uk>2023-11-23 19:54:04 +0000
commit3a51dc3fc0c2403de999c3b5d9c509f26e2bab4b (patch)
tree4135b1b6ce58379a49893f25a24757ec527906d9 /contrib/check-params-in-docs.py
parent7646b5d88056cf269ff555afe95bc361dcf5e5c0 (diff)
downloadgcc-3a51dc3fc0c2403de999c3b5d9c509f26e2bab4b.zip
gcc-3a51dc3fc0c2403de999c3b5d9c509f26e2bab4b.tar.gz
gcc-3a51dc3fc0c2403de999c3b5d9c509f26e2bab4b.tar.bz2
testsuite, lib: Re-allow mulitple function start labels.
The change applied in r14-5760-g2a46e0e7e20 changed the behaviour of functions with assembly like: bar: __acle_se_bar: Where both bar and __acle_se_bar are globals refering to the same function body. The old behaviour overrides 'bar' with '__acle_se_bar' and the scan tests for that label. The change here re-allows the override. Case like this are not legal Mach-O (where two global symbols cannot have the same address in the assembler output). However, given the constraints on the Mach-O scanning, it does not seem that it is necessary to skip the change (any incorrect case should be easily evident in the assembler). gcc/testsuite/ChangeLog: * lib/scanasm.exp: Allow multiple function start symbols, taking the last as the function name. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
Diffstat (limited to 'contrib/check-params-in-docs.py')
0 files changed, 0 insertions, 0 deletions