Closed Bug 813989 Opened 12 years ago Closed 8 years ago

PGO Windows builds output "PGOCVT : fatal error PG0001: An unexpected internal error was detected in source file 'f:\dd\vctools\compiler\utc\src\tools\pogo\cvtpgd\cvtpgd.cpp', line 800." during the run, but still succeed

Categories

(Firefox Build System :: General, defect)

All
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: emorley, Assigned: jesup)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

eg:
{
Generating code
e:\builds\moz2_slave\m-cen-w32-pgo\build\layout\style\nscssparser.cpp(1071) : warning C4748: /GS can not protect parameters and local variables from local buffer overrun because optimizations are disabled in function
Finished generating code
PGOCVT : fatal error PG0001: An unexpected internal error was detected in source file 'f:\dd\vctools\compiler\utc\src\tools\pogo\cvtpgd\cvtpgd.cpp', line 800.
PGOCVT : fatal error PG0001: An unexpected internal error was detected in source file 'f:\dd\vctools\compiler\utc\src\tools\pogo\cvtpgd\cvtpgd.cpp', line 858.
}

https://tbpl.mozilla.org/php/getParsedLog.php?id=17232269&tree=Firefox

We should either fix this error or if it is expected, then suppress it.

It unfortunately shows in the TBPL annotated summary due to "fatal error", so is confusing people (including myself initially) as to real cause when things break.
This is an internal compiler error, so the only thing we can do is work around it. From the context, it's possible it is occurring while compiling nscssparser.cpp. Do you have any idea of the regression range here?
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #1)
> This is an internal compiler error, so the only thing we can do is work
> around it. From the context, it's possible it is occurring while compiling
> nscssparser.cpp. Do you have any idea of the regression range here?

Err... it's present on beta but not release... :-/
Keywords: regression
I'll bisect this on Try
Assignee: nobody → edmorley.bz
Status: NEW → ASSIGNED
Maybe they came into m-c in the same push? Try checking the inbound pushlog?
Yeah they did, it's just annoying to not be able to link to a regression range if it's inside a single push.
(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #7)
> Built from https://hg.mozilla.org/mozilla-central/rev/0ea0cfc7f6f4
> -> https://tbpl.mozilla.org/?tree=Try&rev=fe0fb33147a4

Bad
(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #11)
> Built from https://hg.mozilla.org/mozilla-central/rev/a2630fb2dbfa
> -> https://tbpl.mozilla.org/?tree=Try&rev=acc57cf677ac

Good

> Built from https://hg.mozilla.org/mozilla-central/rev/7dda68e6ffba
> -> https://tbpl.mozilla.org/?tree=Try&rev=97295af352b0

Bad

New range:

Last known good: a2630fb2dbfa
First known bad: 7dda68e6ffba

In that range:
	7dda68e6ffba	Randell Jesup — Bug 797671: cleanup from importing webrtc.org update r=ted,glandium (Part is bug 778801 r=derf)
	174d772e83f4	Randell Jesup — Bug 797671: Import Webrtc.org code from stable branch 3.12 (rev 2820) rs=jesup
	6a76b682c628	Benoit Jacob — Bug 797526 - some assertions in nsDOMClassInfo should be fatal in debug builds - r=bz
	68dd2bcc51ee	Jeff Muizelaar — Bug 792199. Only decode visible images immediately when switching to a tab. r=joe This creates a new method 'StartDecoding' which does a RequestDecode and some decoding of the image.
Presuming it's the webrtc import, one last run to confirm.

Built from https://hg.mozilla.org/mozilla-central/rev/6a76b682c628
-> https://tbpl.mozilla.org/?tree=Try&rev=92abb61cfdde
New range:

Last known good: 6a76b682c628
First known bad: 7dda68e6ffba

In that range:
	7dda68e6ffba	Randell Jesup — Bug 797671: cleanup from importing webrtc.org update r=ted,glandium (Part is bug 778801 r=derf)
	174d772e83f4	Randell Jesup — Bug 797671: Import Webrtc.org code from stable branch 3.12 (rev 2820) rs=jesup
Assignee: edmorley.bz → nobody
Blocks: 797671
Randell, are you ok to run point on this? :-)
Flags: needinfo?(rjesup)
Status: ASSIGNED → NEW
Sure.  Amazing it went that long without being noticed.

Almost certainly the https://hg.mozilla.org/mozilla-central/rev/174d772e83f4 patch - which is a slim 15 MB

Taking point, but wouldn't mind some help isolating it....
Assignee: nobody → rjesup
Flags: needinfo?(rjesup)
WINNT 5.2 mozilla-b2g18 build on 2013-03-20 15:27:46 PDT for push e7996a13db8b
slave: w64-ix-slave16

https://tbpl.mozilla.org/php/getParsedLog.php?id=20910450&tree=Mozilla-B2g18
Blocks: log-SnR
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.