Weird change in allocation numbers of T9203
|Reported by:||nomeata||Owned by:||simonmar|
|Type of failure:||None/Unknown||Test Case:|
|Related Tickets:||#8096||Differential Rev(s):|
Description (last modified by )
While trying to improve our handle on allocation numbers, I’m stuck with the test case T9203. On some machines, it allocates roughly 95747304 bytes (this includes travis and my laptop), on others 42946176 bytes (e.g. on the machine where I monitor benchmark performance). All machines are 64 bit Linux machines.
The output of
-ddump-cmm is identical (up to variable names). Even
-ddump-asm looks the same, besides some jump target reordering. The binary runs too small to get a heap profile.
I’m a bit stuck here: What can be the cause for these differences?
(BTW, if have an up-to-date GHC tree, can you report the number you get? Run
make -C testsuite VERBOSE=4 TEST=T9203 for that.)