RFR(XS): 8144930: gcc 4.1.2: fix build flags after "8114853 variable tracking size limit exceeded"

[Lindenmaier, Goetz]

You are right. I had gcc 4.8 in the path on the machine where I ususally 
build with 4.3.  

I'd like to test for >= 4.8 instead, as I have no 4.5 available to test.
Is that ok with you?

(This does not break our builds, so there is no hurry from our side.)

Best regards,
  Goetz.


-----Original Message-----
From: Kim Barrett [mailto:kim.barrett at oracle.com] 
Sent: Thursday, December 10, 2015 1:49 AM
To: David Holmes <david.holmes at oracle.com>
Cc: Lindenmaier, Goetz <goetz.lindenmaier at sap.com>; hotspot-runtime-dev at openjdk.java.net
Subject: Re: RFR(XS): 8144930: gcc 4.1.2: fix build flags after "8114853 variable tracking size limit exceeded"

On Dec 9, 2015, at 2:58 AM, David Holmes <david.holmes at oracle.com> wrote:
> 
> On 9/12/2015 5:31 PM, Lindenmaier, Goetz wrote:
>> Hi David,
>> 
>> thanks for sposonring!  This was quick!
> 
> Trivial change :)

Sorry for my late arrival, but the change may not be quite correct.

It makes the use of -fno-var-tracking-assignments conditional on gcc4.3+.  However, according to gcc documentation, that flag doesn't appear until gcc4.5.  (I don't have access to any of the relevant versions to see if the option is supported without documentation.)