RFR(M) : 7104565 : trim jprt build targets
Vladimir Kozlov
vladimir.kozlov at oracle.com
Thu Apr 4 07:41:47 PDT 2013
It was very long broken (before 1.5) and never was repaired. It was used
before we had decent profiling tools. Just delete all 'profiled' related
files.
Thanks,
Vladimir
On 4/4/13 4:08 AM, David Chase wrote:
>
> On 2013-04-04, at 3:11 AM, Stefan Karlsson <stefan.karlsson at oracle.com> wrote:
>
>> David,
>>
>> You change a lot of make files and this will affect all HotSpot developers, so this review should probably go to hotspot-dev and not hotspot-compiler-dev.
>>
>> Have you tried these changes with a full JDK8 forest and the new build infrastructure?
>
> I can do that. Does JPRT use new or old build? (if it does, then in some sense I have already tested that way, and if it does not, then it is pointless to re-run JPRT on the full tree.)
>
> Two questions -- I noticed that I missed two versions of profiled.make (i.e., those files could be deleted). But I am also unsure about the wisdom of getting rid of profiled make -- what is our method of profiling hotspot, if we do not have that build option?
>
> David
>
More information about the hotspot-compiler-dev
mailing list