head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.64
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.62
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.60
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.58
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.56
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.54
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.52
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.50
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.48
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.46
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.44
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.42
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.40
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.38
	pkgsrc-2022Q4-base:1.1
	pkgsrc-2022Q3:1.1.0.36
	pkgsrc-2022Q3-base:1.1
	pkgsrc-2022Q2:1.1.0.34
	pkgsrc-2022Q2-base:1.1
	pkgsrc-2022Q1:1.1.0.32
	pkgsrc-2022Q1-base:1.1
	pkgsrc-2021Q4:1.1.0.30
	pkgsrc-2021Q4-base:1.1
	pkgsrc-2021Q3:1.1.0.28
	pkgsrc-2021Q3-base:1.1
	pkgsrc-2021Q2:1.1.0.26
	pkgsrc-2021Q2-base:1.1
	pkgsrc-2021Q1:1.1.0.24
	pkgsrc-2021Q1-base:1.1
	pkgsrc-2020Q4:1.1.0.22
	pkgsrc-2020Q4-base:1.1
	pkgsrc-2020Q3:1.1.0.20
	pkgsrc-2020Q3-base:1.1
	pkgsrc-2020Q2:1.1.0.18
	pkgsrc-2020Q2-base:1.1
	pkgsrc-2020Q1:1.1.0.14
	pkgsrc-2020Q1-base:1.1
	pkgsrc-2019Q4:1.1.0.16
	pkgsrc-2019Q4-base:1.1
	pkgsrc-2019Q3:1.1.0.12
	pkgsrc-2019Q3-base:1.1
	pkgsrc-2019Q2:1.1.0.10
	pkgsrc-2019Q2-base:1.1
	pkgsrc-2019Q1:1.1.0.8
	pkgsrc-2019Q1-base:1.1
	pkgsrc-2018Q4:1.1.0.6
	pkgsrc-2018Q4-base:1.1
	pkgsrc-2018Q3:1.1.0.4
	pkgsrc-2018Q3-base:1.1
	pkgsrc-2018Q2:1.1.0.2
	pkgsrc-2018Q2-base:1.1;
locks; strict;
comment	@// @;


1.1
date	2018.05.02.12.42.51;	author jperkin;	state Exp;
branches;
next	;
commitid	c6Ouwv7Es2pvJIAA;


desc
@@


1.1
log
@spidermonkey185: Fix SunOS/x86_64 mmap handling.

The previous MAP_32BIT workaround was insufficient, SpiderMonkey still makes
certain assumptions about memory layout, requiring that the high 17 bits are
clear.  This was most noticeable with couchdb's couchjs process that would
reliably segfault.

Instead, apply a mixture of Debian and upstream patches to implement their
ia64 workaround on SunOS/x86_64, utilising both a fixed mmap range and
disabling static strings to workaround this issue.

Tested with the couchdb test suite which now runs to completion.

Bump PKGREVISION.
@
text
@$NetBSD$

Implement Debian disable-static-strings-on-ia64.patch fix.

--- tracejit/Writer.cpp.orig	2011-03-31 19:08:36.000000000 +0000
+++ tracejit/Writer.cpp
@@@@ -246,7 +246,9 @@@@ couldBeObjectOrString(LIns *ins)
         // ins = andq ins_oprnd1, ins_oprnd2
         ret = true;
 #endif
-    } else if (ins->isop(LIR_addp) &&
+    }
+#ifdef JS_HAS_STATIC_STRINGS
+	else if (ins->isop(LIR_addp) &&
                ((ins->oprnd1()->isImmP() &&
                  (void *)ins->oprnd1()->immP() == JSString::unitStringTable) ||
                 (ins->oprnd2()->isImmP() &&
@@@@ -258,6 +260,7 @@@@ couldBeObjectOrString(LIns *ins)
         // ins = addp JSString::unitStringTable, ...
         ret = true;
     }
+#endif
 
     return ret;
 }
@