diff options
author | Colin Walters <walters@verbum.org> | 2012-11-06 11:48:36 -0500 |
---|---|---|
committer | Colin Walters <walters@verbum.org> | 2012-11-12 11:43:09 -0500 |
commit | ac7376e0b2671ac6cb12c69b0289e029a3c2302b (patch) | |
tree | dde072db0d69568ab9d027b35599ff28fcaaa20f /giscanner/sourcescanner.h | |
parent | 75148f33bbff9eed6164c0c02c584916fd127396 (diff) | |
download | gobject-introspection-ac7376e0b2671ac6cb12c69b0289e029a3c2302b.tar.gz |
scanner: Correctly handle large 64 bit integer constants
In C, positive integer constants are by default unsigned. This means
an expression like 0x8000000000000000 will be "unsigned long long".
In the actual scanner code, we were parsing them as "gint64", and
storing them as gint64. This was incorrect; we need to parse them
as guint64, and store the bits we get from that. This gives us
an equivalent result to what the C compiler does.
However, when we actually return the value as a Python "long"
(arbitrary length integer), we need to treat the value as unsigned if
the result indicated it was.
https://bugzilla.gnome.org/show_bug.cgi?id=685022
Conflicts:
tests/scanner/Regress-1.0-expected.gir
tests/scanner/regress.h
Diffstat (limited to 'giscanner/sourcescanner.h')
-rw-r--r-- | giscanner/sourcescanner.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/giscanner/sourcescanner.h b/giscanner/sourcescanner.h index df16cf6a..a2834caf 100644 --- a/giscanner/sourcescanner.h +++ b/giscanner/sourcescanner.h @@ -126,6 +126,7 @@ struct _GISourceSymbol gboolean const_int_set; gboolean private; gint64 const_int; /* 64-bit we can handle signed and unsigned 32-bit values */ + gboolean const_int_is_unsigned; char *const_string; gboolean const_double_set; double const_double; |