Make code-coverage builds use GCC 4.3

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
9 years ago
5 years ago

People

(Reporter: Benjamin Smedberg, Assigned: catlee)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
In bug 512712 I upgraded mozilla-central and the project branches to use GCC 4.3 on Linux i386.  We should probably do the same for code-coverage builds, although I don't know much about the setup there and whether there is a special compiler being used.
I think there would be no issues with this upgrade. I do not remember a specific dependency on GCC version as long as the GCC and GCOV are from the same version.

Comment 2

9 years ago
Is this a config change request, or a compiler upgrade on the build machine request?

Aiui, code coverage is run on the same slaves as other builds, so they should all have gcc 4.3.
(Reporter)

Comment 3

9 years ago
Config change, as in bug 512712. I just wasn't sure whether the new compiler worked for code coverage.
The latest run [ Dated 2009-09-06 ] still uses gcc 4.1.1 

Can you please make changes and start a special run so that I can verify if the results look good. As I have mentioned earlier, there should be no problem in the instrumented build mode with gcc upgrade [ I hope ]

Thanks
Murali
(Assignee)

Comment 5

9 years ago
Created attachment 399550 [details] [diff] [review]
Use gcc433 for code coverage builds
Assignee: nobody → catlee
Attachment #399550 - Flags: review?(bhearsum)
Attachment #399550 - Flags: review?(bhearsum) → review+
Is it done ?

Latest results seem not to reflect this.
(Assignee)

Comment 7

9 years ago
Comment on attachment 399550 [details] [diff] [review]
Use gcc433 for code coverage builds

changeset:   1519:e7d220dbad99
Attachment #399550 - Flags: checked-in+
(Assignee)

Comment 8

9 years ago
Next run will be using gcc 4.3.  Re-open, or file a new bug if there are problems.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.