On Jul 31, 8:51pm, tsut...@ceres.dti.ne.jp (Izumi Tsutsui) wrote: -- Subject: Re: CVS commit: src/sys/arch/sparc
| christos@ wrote: | | Why don't you guys (as core? or individual developer?) post | an announcement that mentions benefit of -fno-common and | ask Tier II users to fix possible fallout, before putting | random MD fixes that would cause annoying silent hangs? I can say the same for the port-masters who leave their ports broken for days. But the benefits of -fno-common are pretty obvious: mistakes like having char *foo in one file and int foo in another, now will cause a build failure. | For sparc, the correct place seems in sparc/autoconf.c:bootstrap(). | For sun2 it's sun2/locore2.c:_bootstrap(). | Most other m68k ports foo_init() for pre-main initialization. It would be nice if the individual port-masters would proactively check their ports so that they would remain buildable, and people who have cross-port knowledge like you, would work to harmonize these disparate and undocumented interfaces. christos
