Ticket #3984 (accepted enhancement)

Opened 7 years ago

Last modified 6 years ago

Do we need to switch to ints instead of unsigned ints for size types?

Reported by: gemacke Owned by: gemacke
Priority: normal Milestone: 1.2
Version: 1.0 Severity: normal
Keywords: Cc:

Description

As part of the recent fix to bug 759547 in release 1.5 of the XMT runtime, certain optimizations for unsigned integers have been turned off by default. There were problems caused by overflows due to unsigned ints having values greater than those storable by signed ints.

Is this going to impact performance of MTGL considering that we use unsigned long (same as unsigned int on XMT) for most of our size types? Should we change to using long instead? It is unlikely that any of our size types will be larger than the value held by a 64 bit integer. From a design standpoint, it makes more sense to have unsigned integer values as that is what the underlying data really is, however, if it is necessary to get better performance, I don't see a problem with switching to signed integers.

Change History

comment:1 Changed 7 years ago by gemacke

  • Status changed from new to accepted

comment:2 Changed 6 years ago by gemacke

  • component Eldorado deleted

comment:3 Changed 6 years ago by gemacke

  • Version set to 1.1
  • Milestone set to 1.0

comment:4 Changed 6 years ago by gemacke

  • Version changed from 1.1 to 1.0
  • Milestone changed from 1.0 to 1.1

comment:5 Changed 6 years ago by gemacke

  • Milestone changed from 1.1 to 1.2
Note: See TracTickets for help on using tickets.