> On Dec 9, 2015, at 10:05 AM, Nick Wellnhofer via swift-dev > <swift-dev@swift.org> wrote: > > On 09/12/2015 18:55, Nick Wellnhofer via swift-dev wrote: >>> Is there a better way to get that symbol, and why wasn’t this a problem for >>> x86_64? >> >> AFAICS, this is a problem for x86_64 Linux. It's not a problem on Apple >> platforms, because there C++ binaries are linked with compiler-rt instead of >> the GCC runtime. > > Ah, you probably meant why __mulodi4 isn't a problem on x86_64 Linux. I think > that's because it's defined by the 64-bit GCC runtime. (clang on Linux uses > the GCC runtime AFAIK.)
Right, libgcc doesn't provide 128-bit integer entry points on 32-bit platforms, and doesn't provide the overflow-checking variant __muloti4 at all AFAIK. -Joe _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
