Backporting an AsyncGetCallTrace patch to OpenJDK6

Mark Wielaard mark at
Tue Sep 9 09:15:07 PDT 2008

Hi Daniel,

On Tue, 2008-09-09 at 08:24 -0600, Daniel D. Daugherty wrote:
> Mark Wielaard wrote: 
> > If I am interested in a specific HSX version, how would I find out when
> > that version was checked into the repo?
> I believe you'll be able to figure that out from the "hg log"
> of the "make/hotspot_version" file. In theory, the folks who
> pushed the updates the "make/hotspot_version" file will have
> included some comment that indicates the change to the HSX
> version number. That should give you the changeset ID for the
> last change that comprises the specific HSX version.

Thanks. I see hg log -v will give me the information I was looking for
since HS_* numbers are updated in a specific commit. What does it mean
for each of these, HS_MAJOR_VER, HS_MINOR_VER and HS_BUILD_NUMBER, to be
incremented? Or is there no meaning attached and are they more or less
random, date based, tags?

> > Is there a way to match the
> > hotspot mercurial rev number to a HSX version number?  
> See above reply. I don't think we're tagging the repros with
> the HSX version number, but perhaps we should. I know we tag
> the JDK7 repos with the JDK7 build number, but I don't think
> we tag the hotspot repos with the HSX version number.

I think that would be beneficial, if there is some meaning attached to
the specific numbers when they are increased. Then someone can make sure
they pick a "stable" or "production" ready version from the hotspot
(jdk7) repository to push into their project.

That is really why I asked, to make sure that I know that when we push
an hotspot version into icedtea (which comes with 2 different versions,
depending on whether or not you build against zero/shark) it is
something that is stable enough and something that the hotspot devs
wouldn't feel uncomfortable with being in a bit wider use.



More information about the hotspot-dev mailing list