Open
Bug 1445773
Opened 7 years ago
Updated 2 years ago
Clean up the SOURCES section in js/src/moz.build
Categories
(Core :: JavaScript Engine, enhancement, P3)
Tracking
()
NEW
People
(Reporter: RyanVM, Unassigned)
Details
(In reply to David Major [:dmajor] from bug 1086964 comment #12)
> Probably the same for CTypes.cpp ...and actually it looks like there's a ton
> of stuff in this moz.build with no clear reason for using SOURCES. Do you
> feel like cleaning these up in a followup?
Reporter | ||
Comment 1•7 years ago
|
||
Just a note that moving RegExp.cpp into UNIFIED_SOURCES caused a lot of win32 orange in CI when I tried making that change in bug 1086964. Lots of timeouts suggesting big slowdowns.
Comment 2•7 years ago
|
||
Thanks for updating the comment for RegExp.cpp.
I agree it's unclear whether some of those comments still apply (and, in some cases, what they even mean). Would be great to see this list trimmed.
Priority: -- → P3
(In reply to Jason Orendorff [:jorendorff] from comment #2)
> Thanks for updating the comment for RegExp.cpp.
>
> I agree it's unclear whether some of those comments still apply (and, in
> some cases, what they even mean). Would be great to see this list trimmed.
Mostly, the files I had in mind were the ones that don't even have comments. There's a whole bunch of
if CONFIG["FOO"]:
SOURCES += foo.cpp
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•