TP1.0 took about 32K of RAM to run IIRC on CP/M. I don't remember exactly the size of the full "distribution", but I think it was under 200K, all files included.
As to bloat and time wasted, that is true to a large extent, but the merit of tailoring your own toolchain goes beyond just saving a few tens of MB IMO - which is why I said that I thought configuring and building it yourself, for someone who wants more control, was way more beneficial that just trying to strip an existing one until it stops working. But it's all a matter of perspective and needs. I don't do that for ARM toolchains, but I do maintain my own RISC-V toolchain.
Those were the days
I implemented CP/M 2.2 on a Z80, but on a Z180 I cheated and the BIOS was 64k and was banked-in when called
In this case I would be well stumped by the ~70 libc.a builds. It would be viable on a project which never changes except around the edges. I mean, you hardly need to update GCC, unless you feel bored and need work to find out why v n+1 is producing new warnings
THANKS all for your contribution in this thread.
As a conclusion It's more a waste of time than a waste of HDD space !