Date: Sat, 27 Mar 2004 13:57:00 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Cyrille Lefevre" <cyrille.lefevre@laposte.net> Cc: arch@freebsd.org Subject: Re: posix ps (was Re: Adding `pgrep' and `pkill' to /usr/bin) Message-ID: <p060204a9bc8b7a53ea0b@[128.113.24.47]> In-Reply-To: <1c0901c413e8$04a466c0$7890a8c0@dyndns.org> References: <p0602046abc879c5fe2f9@[128.113.24.47]> <20040325070120.GA67497@VARK.homeunix.com> <1a9c01c41359$b3da45e0$7890a8c0@dyndns.org> <p06020494bc8a5738af2f@[128.113.24.47]> <1c0901c413e8$04a466c0$7890a8c0@dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:41 AM +0100 3/27/04, Cyrille Lefevre wrote: >"Garance A Drosihn" <drosih@rpi.edu> wrote: >as I read your proposed changes, we could merge them w/o >any problem. well, in fact, I already merge some of them >(the or part instead of and). > >original ps : 26668 (no posix compliant) >yours (gad) : 31072 (partly posix compliant) >mine (cyrille) : 35684 (fully posix compliant) Arg. It looks like I must have added another few instructions somewhere, and triggered the same size-increase that I talked about in the "Adventures with gcc: code vs object-code size" thread on the freebsd-hackers. In that case, adding 40 bytes of new instructions to one routine in ps.o caused /bin/ps to jump by 3940 bytes. As long as I had avoided whatever that threshold was, I was able to keep the size down around 27000 bytes. And that was for a version which *included* the -R, -s, and new -g options. Man that's annoying, I had been doing so good with it... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p060204a9bc8b7a53ea0b>