Date: Wed, 3 Apr 2002 09:02:12 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Dominic Marks <dominic_marks@btinternet.com> Cc: Jeroen Ruigrok/asmodai <asmodai@wxs.nl>, Kenneth Culver <culverk@alpha.yumyumyum.org>, Dag-Erling Smorgrav <des@ofug.org>, Mike Barcroft <mike@FreeBSD.ORG>, "M. Warner Losh" <imp@village.org>, jake@locore.ca, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 critical.c src/sys/i386/include cpufunc.h critical.h src/sys/i386/isa apic_vector.s icu_vector.s src/sys/kern kern_fork.c kern_proc.c kern_switch.c src/sys/alpha/alph Message-ID: <200204031702.g33H2CH40336@apollo.backplane.com> References: <xzplmc5u6rp.fsf@flood.ping.uio.no> <20020402163939.M47850-100000@alpha.yumyumyum.org> <20020403052504.GJ78613@daemon.ninth-circle.org> <20020403151536.C3198@host213-123-131-244.in-addr.bto>
next in thread | previous in thread | raw e-mail | index | archive | help
:> top makes a lot of sense.] :> :> The parser has to iterate 8 times instead of 1 time for a single tab :> character. :> :> How much gain you really get I don't know, that would need to be timed. :> :> You can always look at: http://ccache.samba.org/ to improve compilation :> speed. Actually, its the lexer that has to loop on the whitespace, not the parser. I would not expect whitespace to make much of a difference. In DICE whitespace was the first thing I checked for and it was dealt with in a tight loop. Since preprocessing tends to generate a lot of whitespace, I would be very surprised if GCC didn't optimize it too. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204031702.g33H2CH40336>