Closed
Bug 653322
Opened 14 years ago
Closed 2 years ago
Remove PGO workaround by Bug 640494
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: m_kato, Assigned: m_kato)
References
Details
As long as I test on Win64 PGO with VC9 x64, it is unnecessary to hack for bug 640494. It should be on MSVC x86 only.
Win64 build uses VC9SP1 on tinderbox.
Assignee | ||
Updated•14 years ago
|
Hardware: x86 → x86_64
Comment 1•14 years ago
|
||
Are you aware there's bug 653322, already?
Comment 2•14 years ago
|
||
Comment 3•14 years ago
|
||
Damn copy/paste. I meant bug 653056.
Comment 4•14 years ago
|
||
Note that this is most likely a compiler problem, so even x86 VC9 might be working. I'm trying to get a local build off x86 VC8sp1, but that it fails to link xul.lib in the first pass...
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to comment #4)
> Note that this is most likely a compiler problem, so even x86 VC9 might be
> working. I'm trying to get a local build off x86 VC8sp1, but that it fails to
> link xul.lib in the first pass...
Although I don't test on VC9SP1 x86, should I test using VC9SP1 x86?
PGO compiler sometimes generates incorrect code if using MMX, SSE and FP (such as bug 413019).
Assignee | ||
Comment 6•14 years ago
|
||
Also, as long as I know, we have a plan to switch to VC10 if Bug 515492 is fixed. (VC10 has no build-able CRT code.) So it may be unnecessary to test VC9SP1 x86.
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•