This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
- From: "mrs at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 26 Sep 2016 16:12:43 +0000
- Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
- Auto-submitted: auto-generated
- References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
--- Comment #13 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> ---
The change in c12 is ok if you'd like to do that. The only problem with it is
that then we will not be able to discover when radr://19802258 is fixed. When
people notice that that bug is fixed, we should revert the c12 patch.
Essentially, we allow the test case to track any _other_ issue that prevents
things from just working (to catch any regressions), so that when ld64 is
fixed, the test case will remain working.