https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #15 from Jeremy Huddleston Sequoia <jeremyhu at macports dot org> --- (In reply to John Marshall from comment #14) > [In reply to Jeremy Huddleston Sequoia in comment #12] > > In the future, please file radars for these problems and ping me directly if > you want. Issues in macOS headers don't get fixed if we don't know about > them, > and I'd prefer to fix the SDK itself than have GCC use fixup hacks. > [snip] > The __OSX_AVAILABLE_STARTING issue still exists in the GM SDK as it was never > reported to Apple AFAIK. I've filed a radar now to track it: > <rdar://problem/55937005>. > > Thanks for the advice. I reported this to Apple in early June (FB6125120), > as noted in comment #4 above. Looking at it in > feedbackassistant.apple.com<http://feedbackassistant.apple.com> today, there > is no real indication anyone at Apple has ever read it. So that's > unfortunate. Thanks for the pointer to your report, John. I looked it up, and an engineer sent it back to ADC a couple weeks after you filed it as a duplicate of <rdar://problem/51499580>. 51499580 is the one I filed (actually on the same day as yours) for the __has_builtin usage in Availability.h AvailabilityInternal.h and TargetConditionals.h. Those were addressed, but that wasnt't the entirety of the issues across the entire SDK. The comments in the report were unfortunately not as detailed as the comments in this bugzilla report, so the engineer that screened it just thought it was addressed with the fix to the bug I reported. Sorry we missed that, and I'm sorry that ADC hasn't responded back to you. I'm going to ping them to figure out why this is still in their "send a response" queue. As for bullets in Rainer's original report here, I believe #2,#4 were addressed by the fix to my radar. #1 did not get fixed before GM, but we have a radar tracking it (56133558) that was filed by Homebrew. #3 (dyld) looks to no longer be an issue in the GM headers. Can you please confirm? I just did a visual check of the file and didn't notice an issue. In the future, please feel free to poke me directly via email when you file a report like this as I will definitely work to get a fix into the earliest possible release. These types of issues are a personal pet peeve of mine ;)
