From mboxrd@z Thu Jan 1 00:00:00 1970 From: jtc@redback.com (J.T. Conklin) To: gdb@sourceware.cygnus.com Subject: dcache Date: Thu, 15 Jun 2000 15:58:00 -0000 Message-id: <5mem5y1rj2.fsf@jtc.redback.com> X-SW-Source: 2000-06/msg00134.html The dcache_flush() routine throws away its contents. I don't know about you guys, but to me flushing a cache implies writing out the contents, is there any objection to renaming this function to some- thing like dcache_invalidate()? The dcache_writeback() function is a real cache flush, but writeback is just as descriptive. I see no reason to rename it to dcache_flush(). The following comment within dcache.c: In general the dcache speeds up performance, some speed improvement comes from the actual caching mechanism, but the major gain is in the reduction of the remote protocol overhead; instead of reading or writing a large area of memory in 4 byte requests, the cache bundles up the requests into 32 byte (actually LINE_SIZE) chunks. Reducing the overhead to an eighth of what it was. This is very obvious when displaying a large amount of data, Implies that GDB writes reads and memory in small chunks instead of larger chunks, and the dcache speeds this up by coalescing multiple small transactions into larger ones. Does anyone know the truth of this implication, especially for writes? I ask because the current implementation is a writethrough cache --- small writes aren't going to be combined. I suspect in most cases, if target memory is cached at all, this is the desired behavior. (e.g. A user setting a global flag probably wants that change to be reflected immediately, so that another thread of execution can act upon it). Are there any circumstances where a writeback cache would be useful? While I'm fiddling around with dcache, it would not be difficult to add. Every place there's a dcache_flush() in target code would be replaced with something like dcache_writebackinvalidate(), and the dcache_xfer_memory could avoid writing the data if the memory region was configured for a writeback behavior. --jtc -- J.T. Conklin RedBack Networks >From kwho@visto.com Thu Jun 15 19:12:00 2000 From: "Ka Wai Ho" To: gdb@sourceware.cygnus.com Subject: Ver 5.0 Configuration Problem with DJGPP Date: Thu, 15 Jun 2000 19:12:00 -0000 Message-id: <1666.961121547.0@NO-ID-FOUND.mhonarc.org> X-SW-Source: 2000-06/msg00135.html Content-length: 2116 Dear Sir, I get the follow message when configure GDB 5.0 D:\DJGPP\gdb-5.0>sh ./gdb/config/djgpp/djconfig.sh Checking the unpacked distribution... ok. Editing configure scripts for DJGPP... Running the configure script... Config.guess failed to determine the host type. You need to specify one. Usage: configure [OPTIONS] [HOST] Options: [defaults in brackets] --prefix=MYDIR install into MYDIR [/usr/local] --exec-prefix=MYDIR install host-dependent files into MYDIR [/usr/local] --help print this message [normal config] --build=BUILD configure for building on BUILD [BUILD=HOST] --host=HOST configure for HOST [determined via config.guess] --norecursion configure this directory only [recurse] --program-prefix=FOO prepend FOO to installed program names [""] --program-suffix=FOO append FOO to installed program names [""] --program-transform-name=P transform installed names by sed pattern P [""] --site=SITE configure with site-specific makefile for SITE --srcdir=DIR find the sources in DIR [. or ..] --target=TARGET configure for TARGET [TARGET=HOST] --tmpdir=TMPDIR create temporary files in TMPDIR [/tmp] --nfp configure for software floating point [hard float] --with-FOO, --with-FOO=BAR package FOO is available (parameter BAR) --without-FOO package FOO is NOT available --enable-FOO, --enable-FOO=BAR include feature FOO (parameter BAR) --disable-FOO do not include feature FOO Where HOST and TARGET are something like "sparc-sunos", "mips-sgi-irix5", etc. #!/bin/sh # This file was generated automatically by configure. Do not edit. # This directory was configured as follows: d:/djgpp/gdb-5.0/configure --srcdir=d:/djgpp/gdb-5.0 --prefix=${DJDIR} --disable -shared --disable-nls --verbose --enable-build-warnings=-Wimplicit,-Wcomment,-Wf ormat,-Wparentheses,-Wpointer-arith --host=i386-msdosdjgpp --norecursion # using "mh-frag" D:\DJGPP\gdb-5.0> Please help !!! Best Regards, ___________________________________________________________________________ Visit http://www.visto.com/info , your free web-based communications center. Visto.com. Life on the Dot.