summaryrefslogtreecommitdiff
path: root/java/jdk13/files/patch-shared.hpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2004-12-07. Backport some fixes from 1.4 for the HotSpot Server VM when compiledGreg Lewis1-10/+6
under gcc 3.4. In particular, this fixes some places where an enumerated type is assumed to be the same width as an int (which the standard doesn't guarantee and gcc 3.4 now enforces). For full details, see the log for the jdk14 equivalent changes.
2004-10-16. Fix the Server VM for gcc 3.4 part 1/2.Greg Lewis1-0/+38
The HotSpot code (ab)uses named enums as ints in a number of places. The problem with this is that according the the C++ spec, the compiler (essentially) only needs to use an integral type wide enough to hold the values defined in the enum. Earlier versions of gcc appear to have just used an int whether they could have got away with a narrower type or not, hence the code worked as expected. gcc 3.4 now appears to implement this part of the spec, so using an enum blindly as an int causes various problems due to overflow. This case is particularly bogus since the enums are merely to define a named integral type within a class (VMReg::Name doesn't even have any values enumerated in the declaration). So, convert these two enums to simply be typedef'ed ints. Sleuth work, discussion and code suggestions: peadar