Opened 10 years ago
Last modified 9 years ago
#2462 closed enhancement
SpiderMonkey ESR31 upgrade — at Version 13
Reported by: | Yves | Owned by: | Yves |
---|---|---|---|
Priority: | Should Have | Milestone: | Alpha 18 |
Component: | Core engine | Keywords: | spidermonkey javascript |
Cc: | Patch: |
Description (last modified by )
Now that the ESR24 upgrade is done (#1886), I've started working on the ESR31 upgrade. You can test the current WIP version on my github repository (ESR31 branch). Read the readme there for additional information.
Depends on
When updating, don't forget to also fix #2684
Change History (13)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
The better to start on the upgrade now rather than wait until after it's been released ;)
comment:3 by , 10 years ago
But in that case you take the risk that you need to change drastically if the guys @Mozilla do so.
comment:4 by , 10 years ago
There are two big advantages when starting with the upgrade now.
- If we find problems that need to be fixed in SpiderMonkey, we can still get these changes in before the next release. The Firefox (and SpiderMonkey) development starts in the mozilla central repository where big features get integrated. After that it moves to the "Aurora" stage where usually only important bugfixes get applied. This transition will be around the 28th of April, so it's good to start now.
- When updating around once a week, it's easier to figure out the reason if a change breaks something. You can check last week's commit logs or ask people what happened last week. That's harder if you have to search in a period of multiple months.
Sometimes there are bugs and it can take a while to figure out it's not a problem in our code, but the advantages outweight this problem.
comment:5 by , 10 years ago
Description: | modified (diff) |
---|
comment:6 by , 10 years ago
C++11 support is required to use SpiderMonkey 31. I have checked today if patching the headers would be an alternative to avoid that, but it would result in too deep changes. I've replaced all the static_asserts, but then didn't investigate any further when I figured out that the headers also use move constructors. I've created ticket #2669 for the C++11 migration.
comment:13 by , 10 years ago
Description: | modified (diff) |
---|
I thought SpiderMonkey 3.1 will be released in July 2014?
"The next release will be SpiderMonkey 31, around July 2014." https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey