Closed
Bug 611053
Opened 14 years ago
Closed 11 years ago
File Microsoft Connect bug with linkrepro for compiler crash from bug 591836
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ted, Assigned: ted)
References
Details
The patch on bug 591836 caused Visual C++ to crash while attempting to compile (in the link phase, due to WPO/PGO) mozjs+xul. Splitting mozjs back out to its own DLL made the crash go away.
We should file a Microsoft Connect bug with a linkrepro that reproduces the crash.
Filing this bug just to have a way to track this.
The changeset that first introduced the crash was 1af8f0c895bc.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → ted.mielczarek
Blocks: 609976
Assignee | ||
Comment 1•14 years ago
|
||
Just as a data point, I screwed up and forgot to include a profiling command in my build, so it did a PGO build with no profiling data, and it succeeded. This at least indicates that the problem is specific to optimizing with profiling data.
Assignee | ||
Comment 2•14 years ago
|
||
Ok, I reproduced the crash and produced a linkrepro. The only downside is that it's 2GB worth of files. I guess I'll see how well it compresses!
Comment 3•14 years ago
|
||
Was the bug ever reported to
Comment 4•14 years ago
|
||
...Microsoft. I will try to reproduce with VS2010 SP1.
Assignee | ||
Comment 5•14 years ago
|
||
No, I had trouble getting the linkrepro into an actual reproducible state.
Assignee | ||
Comment 6•14 years ago
|
||
That is, I could 100% reproduce the compiler crash, and generate a linkrepro, but then I was unsuccessful in trying to reproduce the link using the linkrepro. It seemed to not have its options right or something. I think perhaps the linkrepro mechanism and PGO are not well integrated or something.
Assignee | ||
Comment 7•11 years ago
|
||
I'm clearly never going to get around to this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•