Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!feeder.news-service.com!news.albasani.net!.POSTED!not-for-mail
From: Jan Burse <janburse@fastmail.fm>
Newsgroups: comp.lang.java.programmer
Subject: Re: Style Police (a rant)
Date: Sat, 27 Aug 2011 18:06:38 +0200
Organization: albasani.net
Lines: 28
Message-ID: <j3b4mn$a2e$1@news.albasani.net>
References: <j39fdc$1hi$1@dont-email.me> <j3akb0$61g$1@news.albasani.net> <j3akn1$6tu$1@news.albasani.net> <d906c374-1751-4b85-b844-fd82569ea9ac@glegroupsg2000goo.googlegroups.com> <j3b49j$8u6$1@news.albasani.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.albasani.net 7xzwzgjlolbOdSuSuWmj/hxgUv/LviaTzPHLeZJSqLjAtDYISpXZnLaR/P2JCZa3+C2gSM7kxyVbFgwSXcnBGWonz6J/XzD9PXyoXEy8ER8RaByJG8laTtjMC0kedSbd
NNTP-Posting-Date: Sat, 27 Aug 2011 16:06:47 +0000 (UTC)
Injection-Info: news.albasani.net; logging-data="M8KCpStVCuwCAVMVOIJkPEZuCaWtBrzLil2zn2yrCWuJ1G5XfjlC6stqni+Hufbi7gNyzZNVi1yW0YPgqa79xapUSLLqN+WhPIWXwi2I4WepPBWqjwWh8pgPFRoOGVGm"; mail-complaints-to="abuse@albasani.net"
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110820 Firefox/6.0 SeaMonkey/2.3.1
In-Reply-To: <j3b49j$8u6$1@news.albasani.net>
Cancel-Lock: sha1:f8mTheybU9EvwcILZYvKCFsz8tc=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:7421

Jan Burse schrieb:
> Without the final keyword a JIT potentially needs to reoptimize
> code, when classes are later loaded. Since although an analysis
> might yield that a class method is actually not overridden,
> it might still get overridden at run time.

Of course the problem is not so much there for JITs that do
call site specific PICs. So a method that is not overridden
will also have not multiple entries in the PICs.

But with the final keyword we can put a closure mark on the
PICs we don't need to bother of extending them at runtime
in case a new method implementation pops up at the call site.
And this could change the realization of the PICs.

So I guess this is not an urban legend. Unfortunately I did
document so much my findings that final has an impact. It
occurs to me once a while. But also I am switching the JDK
a couples of time, i.e. migrating form 32-bit to 64-bit.

With the 64-bit I noticed I different sensitivity profile.
Things that made the 32-bit JDK stumble don't have any impact
at all for the 64-bit. For example the garbage collection runs
very smooth with much less effort.

So not an urban legend but maybe yes a moving target.

Bye