https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #97 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Peter Dyballa from comment #96) > BTW, which of the patch files I used is rather MacPorts related? I have no real way to know. presumably, the base gcc-16.1 upstream checkout is unchanged, then there the addition (probably) of the changes in my development branch (but IDK if that's complete or modified) all the others are macports-related - although you do need the patch-fix-rs6000-host-darwin.diff this is why I/we cannot support this scenario - there is no easy way to know what the state of the input is - and/or how/whether it corresponds to what was released by upstream. In the end, you have to be able to separate things out so that you can say "with this upstream branch and the following conditions, I see bug X" ... and "following conditions" need to be specific so that the issue can be repeated and fixed.
