I am not a reviewer, but
If you want the range of IFS to be short, how about
for mirror in $(IFS=" ," echo ${jib_server_mirrors}); do
assuming you really only want IFS set for the expansion of the values for
mirror. Then you don't have to remember to save and restore it, either.
Can you tell where the reference to ParScanClosure::do_oop_work is
coming from? That method is declared in
hotspot/share/vm/memory/genOopClosures.hpp
(hmm, but it's not declared "inline"), and is then defined inline
in
hotspot/share/vm/memory/genOopClosures.inline.hpp
Maybe we are mis
We (cough) independently discovered the compilation problem with
assembler_i486.hpp and gcc4.1.2. It's bug #6578344, e.g.,
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6578344
and I can see it's fixed in our code base, so it will be published
in the next drop.
... p
Andrew John Hughes wrote:
On 25/01/2008, John Rose <[EMAIL PROTECTED]> wrote:
Hi John,
Thanks for filling us in on what's happening. I'm sure you can
appreciate that from the outside, things look even more forlorn. I'm
sure we all eagerly anticipate the floodgates opening :)
I hope we
If you've figured out where to run such a checker, can we run
pscan on our native sources? Last time I checked, it took 3
seconds to run on a local copy of HotSpot (and found some things
that I fixed). I did try it on all the native code in the JDK,
but I forget how long it took. It wasn't long
with hotspot
that may be after makeDeps is run?
I really like the idea of these kind of scanners being run regularly,
and all the time if possible, but not if they take 12+ hours. :^(
-kto
Peter B. Kessler wrote:
If you've figured out where to run such a checker, can we run
pscan on our nativ
I don't think I invented the stab format. I think stab.h came with adb and sdb,
but might predate even those. Stab.h covers the basics of global symbols,
procedures, source files, line numbers, etc. (The earliest copy I can find is
http://svnweb.freebsd.org/csrg/include/stab.h?revision=12194
