Re: SpiderMonkey 17 Standalone Release

[Sean Stangl]

RC2: http://people.mozilla.org/~sstangl/mozjs17.0.0.rc2.tar.gz

Fixes OpenBSD issues from Bug 735599 and a JSContext destruction issue from Bug 852789.

Robin -- could you verify that Bug 852789 resolved your issue?

Sean

----- Original Message -----
From: "Sean Stangl" <sst...@mozilla.com>
To: dev-tech-...@lists.mozilla.org
Sent: Monday, March 4, 2013 5:29:34 PM
Subject: Re: SpiderMonkey 17 Standalone Release

RC1: http://people.mozilla.org/~sstangl/mozjs17.0.0.rc1.tar.gz

These warnings should now be fixed via clang-specific pragmas. A slew of other clang-only warnings were also fixed.

Thanks for testing!
Sean

----- Original Message -----
From: "Jens Ayton" <mailing-l...@ayton.se>
To: dev-tech-...@lists.mozilla.org
Cc: "Sean Stangl" <sst...@mozilla.com>
Sent: Saturday, March 2, 2013 4:51:08 AM
Subject: Re: SpiderMonkey 17 Standalone Release

On Feb 27, 2013, at 23:45, Sean Stangl <sst...@mozilla.com> wrote:
>
> I am pleased to announce a release candidate for the standalone JS 17 source release, based off Mozilla ESR17:
...
> The plan is to wait roughly a week to gather feedback, with a final release planned for Thursday, March 7th if feedback is positive. Please give feedback either in reply to this post or in Bug 735599.

Under standard conditions on Mac OS X (Xcode 4.6 toolchain, Apple's clang build forked from 3.2, ./configure run without any tweaks) I get:

In file included from .../mozjs17/js/src/jsalloc.cpp:9:
In file included from ./jscntxt.h:17:
./jsapi.h:2585:1: error: 'JS_GetNaNValue' has C-linkage specified, but returns user-defined type 'jsval' (aka 'JS::Value') which is incompatible with C
[-Werror,-Wreturn-type-c-linkage]
JS_GetNaNValue(JSContext *cx);

This also applies to JS_GetNegativeInfinityValue(), JS_GetPositiveInfinityValue(), JS_GetEmptyStringValue(), JS_ComputeThis(), JS_GetReservedSlot() and JS_GetFrameReturnValue().

Suppressing this (-Wno-return-type-c-linkage) lets it build and apparently work.


I also get lots of these:
In file included from .../mozjs17/js/src/jsalloc.cpp:9:
./jscntxt.h:1659:75: warning: deleted function definitions are a C++11 extension [-Wc++11-extensions]
AutoReleaseNullablePtr operator=(const AutoReleaseNullablePtr &other) MOZ_DELETE;
^
./dist/include/mozilla/Attributes.h:196:35: note: expanded from macro 'MOZ_DELETE'
# define MOZ_DELETE = delete

These can be suppressed by adding -Wno-c++11-extensions to OS_CXXFLAGS in autoconf.mk, or by adding -std=c++11 (or gnu++11) somewhere.


There area also lots of -Wcast-aligns ("cast from 'js::types::TypeObjectKey *' to 'js::types::TypeObjectKey **' increases required alignment from 1 to 8" etc).


--
Jens Ayton

_______________________________________________
dev-tech-js-engine mailing list
dev-tech-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine

[Robin Ehrlich]

Yes. The change corrected the problem I was encountering.

Thanks,
Robin

"Sean Stangl" wrote in message
news:mailman.4825.1363898353....@lists.mozilla.org...

[Sean Stangl]

I am pleased to announce the release of SpiderMonkey (MozJS) 17.0.0:

http://ftp.mozilla.org/pub/mozilla.org/js/mozjs17.0.0.tar.gz
MD5: 20b6f8f1140ef6e47daa3b16965c9202

Thanks to everyone involved in finally bringing this release to fruition, especially darkxst, glandium, Ted, Waldo, and dmandelin. Release notes exist at https://developer.mozilla.org/en-US/docs/SpiderMonkey/17 and will be updated in short order.

The next JS major release will be SpiderMonkey 24, around November of this year, tracking the Firefox ESR schedule.

Sean