This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/64883] FAIL: 17_intro/headers/c++*/all_attributes.cc (test for excess errors) on x86_64-apple-darwin14
- From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 31 Jan 2015 22:28:35 +0000
- Subject: [Bug libstdc++/64883] FAIL: 17_intro/headers/c++*/all_attributes.cc (test for excess errors) on x86_64-apple-darwin14
- Auto-submitted: auto-generated
- References: <bug-64883-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
--- Comment #11 from howarth at bromo dot med.uc.edu ---
What is so dangerous about just using...
Index: fixincludes/inclhack.def
===================================================================
--- fixincludes/inclhack.def (revision 220306)
+++ fixincludes/inclhack.def (working copy)
@@ -1266,6 +1266,18 @@ fix = {
};
/*
+ * sys/cdef.sh on Darwin should use reserved name __noreturn__
+ * rather than noreturn.
+ */
+fix = {
+ hackname = darwin_noreturn;
+ mach = "*-*-darwin*";
+ files = sys/cdefs.h;
+ sed = "s/__attribute__((noreturn))/__attribute__((__noreturn__))/g";
+ test_text = "__attribute__((noreturn))";
+};
+
+/*
* __private_extern__ doesn't exist in FSF GCC. Even if it did,
* why would you ever put it in a system header file?
*/
...instead? It seems a whole lot simpler.