{"push_id":2341196546,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"12f2fe0e7d0fa2f7d94fa735781ddd16e33b3e35","before":"891109a9417e6ee58e11fe5d66d116390e5f08d5","commits":[{"sha":"12f2fe0e7d0fa2f7d94fa735781ddd16e33b3e35","author":{"name":"Keith Walker","email":"befa44bf78f99a69f2033aafa4c2d2eda9a48621@arm.com"},"message":"[ARM] disable FPU features when using soft floating point.\n\nTo be compatible with GCC if soft floating point is in effect any FPU\nspecified is effectively ignored, eg,\n\n  -mfloat-abi=soft -fpu=neon\n\nIf any floating point features which require FPU hardware are enabled\nthey must be disable.\n\nThere was some support for doing this for NEON, but it did not handle\nVFP, nor did it prevent the backend from emitting the build attribute\nTag_FP_arch describing the generated code as using the floating point\nhardware if a FPU was specified (even though soft float does not use\nthe FPU).\n\nDisabling the hardware floating point features for targets which are\ncompiling for soft float has meant that some tests which were incorrectly\nchecking for hardware support also needed to be updated. In such cases,\nwhere appropriate the tests have been updated to check compiling for\nsoft float and a non-soft float variant (usually softfp). This was\nusually because the target specified in the test defaulted to soft float.\n\nDifferential Revision: https://reviews.llvm.org/D42569\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@325492 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-project/clang/commits/12f2fe0e7d0fa2f7d94fa735781ddd16e33b3e35"}]}
{"actor":{"display_login":"chapuni"}}