> On 21 Jul 2017, at 20:10, Mike Stump <mikest...@comcast.net> wrote: > > On Jul 21, 2017, at 6:07 AM, Nathan Sidwell <nat...@acm.org> wrote: >> >> [Darwin, cygwin, rx maintainers, you might have an opinion] > > darwin going forward is a DWARF platform, so, shouldn't be a heartache for > real folks.
agreed, in fact the default for current assemblers doesn’t support stabs - and we’ve adjusted the specs to deal with that. > For ancient machines, ancient compilers might be a requirement. Generally, > I like keeping things; but cleanups and removals are a part of life, and > eventually the old should be removed. I'd not stand in the way of such > removal. If we were within 5 years of such a transition point, I'd argue to > keep it for at least 5 years. But, the switch for darwin was Oct 26th, 2007. > 10 years I think is a nice cutover point for first tier things. Beyond 10, > and I'd say, you are dragging your feet. If _all_ the code for DBX were in > my port file, I'd be tempted to keep it indefinitely. It's not, so, that's > not possible/reasonable. > > Iain, do you still have the G5s? :-) Do they run 8 or 9? What do you > think? Seem reasonable? I still have access to i686 and powerpc Darwin8, but testing is extremely infrequent. For the record; anyone wanting modern toolchains on Darwin8 most likely has to face building a linker and more modern cctools anyway(the XCode 2.5 set was extremely flaky from at least 4.6/4.7). I’d suspect that a person serious in doing that would likely be willing to build GDB which does support x86 Darwin, at least. FWIW I have a patch that makes GDB (at least 7.x) work for PowerPC too. If anyone cares, ask ;-) (I doubt if I’ll try modernising it across the transition to c++ for GDB - since available time would prob be better spent elsewhere). Anyone wanting to build modern GCC on < Darwin8 is going to need to build most of the supporting infra too - the (XCode 1.5) linker/assembler there don’t support enough weak stuff to be viable for modern c++. These very old platforms are long past the “config && make” stage, supporting them needs a degree of commitment and understanding. ----- My G5 ( and most of my other ppc hardware) habitually runs 10.5 (Darwin9) and I’ve no motivation to reboot to 10.4 unless to test something more quickly than my really ancient G4s can manage. > The 64_BIT x86 darwin question likely can be be flipped to default to dwarf; > so, even that isn't an issue. It ought to be already, in fact anything (powerpc*/x86/x86-64) >= Darwin9 (OS X 10.5) ought to be defaulting to DWARF already, will check that sometime. cheers, Iain Iain Sandoe CodeSourcery / Mentor Embedded
