Opened 12 years ago
Closed 11 years ago
#763 closed defect (invalid)
32-bit/64-bit MG/MGPP index support
| Reported by: | sjm84 | Owned by: | nobody |
|---|---|---|---|
| Priority: | moderate | Milestone: | 2.86 Release |
| Component: | Collection Building | Severity: | major |
| Keywords: | Cc: |
Description
Sam has developed a version of MG and MGPP that natively uses 64-bit for 'long' and related types such as 'intptr_t'. Note: This is different to the previous approach that defined mg_s_long and mg_u_long and then controlled these to always be the same whether on 32-bit or 64-bit.
The new approach definitely produces indexes that are incompatible between 32-bit and 64-bit architectures. The intention of this ticket is to record the idea that 64-bit versions can read in 32-bit generated indexes. Anywhere a 'long' etc. is read in from the index this should be zero-padded to match the larger size a 64-bit machine uses.
Note:
See TracTickets
for help on using tickets.
This is not a problem. Kathy worked out that the order in which the files were fed to the indexer was causing different sized files. The 32-bit and 64-bit operating systems we were testing on were feeding the files to the indexer in different orders. She sorted the files so that the order was the same on both machines and found that identical files were produced.