https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Daniel Vollmer from comment #20)
> Interesting. The gcc-7.4.0 was the bottled (precompiled) version from
> homebrew, generated on Dec 7th 2018, so I assume it must've been built on
> 10.14.1 or 10.14.2.
10.14.2 implied by the -v output.
> I rebuilt 7.4.0 locally just now (so in 10.14.4), and now I can no longer
> reproduce the problem. I'm not sure what could cause the difference,
> though...
that's always the question - even if it involves a bisection to find it.
> (Also, I had to patch a system header for compiling g++-7.4.0 in
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/ucred.h
> in 10.14.4 to not use _Atomic in C++ mode, as seemingly only clang
> understands that).
That seems rather worrying.. editing system headers is not a good plan.
There's a mechanism for the compiler to use if such tricks prove necessary
(fix-includes).
===
So to try and get some sync .. when you bootstrap GCC, what compiler do you use
for the bootstrap - and what as/ld etc?
====
NOTE: There have been salient patches post 7.4.0 that could affect things -
but, rather than build some arbitrary version of 7.4.1, I'd next suggest seeing
if the issue repeats on 8.3.
My current feeling is that 8.3 is in pretty reasonable shape on Darwin (I have
a bunch of pending patches that ought to make things more robust - will push a
branch in due course).
