This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Allow 64-bit enum values


>>>>> "Siddhesh" == Siddhesh Poyarekar <siddhesh@redhat.com> writes:

Siddhesh> I took a separate approach from the one I took in:
Siddhesh> http://sourceware.org/ml/gdb-patches/2012-02/msg00403.html

Siddhesh> and removed the overloaded meaning of the bitpos location variable to
Siddhesh> fix PR symtab/7259. In the following patch, I introduce a separate
Siddhesh> field_location union member 'enumval' which can accept LONGEST and
Siddhesh> hence expand enum values to 64-bit signed values. With this change,
Siddhesh> bitpos now only is used for (non-negative) offsets into structures,
Siddhesh> since the other overload of bitpos (range bounds) were already
Siddhesh> separated into struct range_bound.

I think this also needs an update in py-type.c:convert_field.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]