diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-06-04 13:17:33 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-06-04 13:17:33 +0200 |
| commit | 7af9baa9faead8155e4459104c30cb1b6a15180e (patch) | |
| tree | f374af83c99ae1de201ea30ac3416e4adf605a72 /gdb/testsuite | |
| parent | 4c4d769ab7b01dab8ff8c66209f992de98095a00 (diff) | |
[gdb/pascal] Fix literal truncation
Make sure we error out on overflow instead of truncating in all cases.
The current implementation of parse_number contains a comment about PR16377,
but that's related to C-like languages. In absence of information of whether
the same fix is needed for pascal, take the conservative approach and keep
behaviour for decimals unchanged.
Tested on x86_64-linux, with a build with --enable-targets=all.
Diffstat (limited to 'gdb/testsuite')
| -rw-r--r-- | gdb/testsuite/gdb.base/parse_number.exp | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp index bedb4d64c5..f9782115b7 100644 --- a/gdb/testsuite/gdb.base/parse_number.exp +++ b/gdb/testsuite/gdb.base/parse_number.exp @@ -214,13 +214,7 @@ proc parse_number { lang n } { return [list "unsigned long long" $n] } else { # Overflow. - if { [c_like $lang] || $lang == "go" } { - return [list $re_overflow $re_overflow] - } else { - # Some truncated value or re_overflow, should be re_overflow. - return [list "((unsigned )?(int|long)|$re_overflow)" \ - ($any|$re_overflow)] - } + return [list $re_overflow $re_overflow] } } |