This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/62018] FAIL: gcc.dg/torture/ftrapv-1.c * execution test on x86_64-apple-darwin13
- From: "iains at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 10 Nov 2014 09:05:22 +0000
- Subject: [Bug target/62018] FAIL: gcc.dg/torture/ftrapv-1.c * execution test on x86_64-apple-darwin13
- Auto-submitted: auto-generated
- References: <bug-62018-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #17 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #16)
> (In reply to rguenther@suse.de from comment #15)
> > Your example directly calling __addvsi3 should suffice for that.
>
> I've filed it (radar #18924081), but I don't expect them to fix anything,
> because it is an undocumented internal function, supported for backward
> compatibility.
if it's part of compiler-rt we can just post a patch on llvm-commits and that
will eventually percolate through to the system. If it's part of libSystem,
then I agree .. they might elect to preserve the status quo.
We can still find a way to fix this for GCC tho.