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 | 4c4d769ab7b01dab8ff8c66209f992de98095a00 (patch) | |
| tree | a9bc6cbd228f0b0a3a6dc1c43ef5d467da7ff933 /gdb/testsuite | |
| parent | a2c0d041fdbf9d661099e31629c96cdd666e8b83 (diff) | |
[gdb/go] 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 go, 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 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp index 87554ccf99..bedb4d64c5 100644 --- a/gdb/testsuite/gdb.base/parse_number.exp +++ b/gdb/testsuite/gdb.base/parse_number.exp @@ -214,7 +214,7 @@ proc parse_number { lang n } { return [list "unsigned long long" $n] } else { # Overflow. - if { [c_like $lang] } { + if { [c_like $lang] || $lang == "go" } { return [list $re_overflow $re_overflow] } else { # Some truncated value or re_overflow, should be re_overflow. |