search for: fixedsize

Hi, Looks ok for native MIPS, I have two failures on debian8: Failing Tests (2): XRay-x86_64-linux :: TestCases/Linux/argv0-log-file-name.cc XRay-x86_64-linux :: TestCases/Linux/fixedsize-logging.cc I'll investigate these failures. Otherwise looks ok. I've uploaded the binaries. 9d5a389c20eb5b3071e6a0504b7cf87d clang+llvm-4.0.0-rc1-mipsel-linux-gnu.tar.xz 655f566cd16740aaa542d94bcea18490 clang+llvm-4.0.0-rc1-mips-linux-gnu.tar.xz c505d9e2f95143492e134b268479246b clang+...

I computed "system.time(diag(30000))" with R 2.12.0 on Fedora 13 Linux with 4 GB RAM and with R 2.14.1 on Windows 7 with 8 GB RAM: Linux (4 GB RAM): 0, 0.21, 0.21 -- a fifth of a second Windows 7 (8 GB RAM): 11.37 7.47 93.19 -- over 1.5 minutes. Moreover, during most of that time, I could not switch windows or get any response from the system. When I first encountered this, I

...;getTypeStoreSizeInBits' in DataLayout -- they're used a few hundred times throughout the codebase, and to properly support scalable types we'd need to return something that isn't just a single integer. Since most backends won't support scalable vectors I suggested having a 'FixedSize' method that just returns the single integer, but it may be better to just leave the existing method as is and create a new method with 'Scalable' or 'VariableLength' or similar in the name to make it more obvious in common code. There's a few places where changes in IR may...

...rived types, a function (getSizeExpressionInBits) to return a pair of >> integers (one to indicate unscaled bits, the other for bits that need to be >> scaled by the runtime multiple) will be added. For backends that do not need to >> deal with scalable types, another function (getFixedSizeExpressionInBits) that >> only returns unscaled bits will be provided, with a debug assert that the type >> isn't scalable. > > Can you explain a bit about what the two integers represent? What's the > "unscaled" part for? 'Unscaled' just means '...