I don't know if it's just me, but in these days of Intel+ARM universal binaries for MacOS, I'd find it very convenient to build these fat binaries in one go, like in the times of Apple's gcc version. This was done thanks to driverdriver.c
However, given that the goal of this fork is to be merged upstream with GCC, maybe this driverdriver.c thing should be a customization not merged upstream.
I don't know the GCC internals myself, so I'm pointing out this suggestion as a wished feature.
I don't know if it's just me, but in these days of Intel+ARM universal binaries for MacOS, I'd find it very convenient to build these fat binaries in one go, like in the times of Apple's gcc version. This was done thanks to driverdriver.c
However, given that the goal of this fork is to be merged upstream with GCC, maybe this driverdriver.c thing should be a customization not merged upstream.
I don't know the GCC internals myself, so I'm pointing out this suggestion as a wished feature.