for arm64, it just needs a few defines so that Mono recognizes the platform as
a valid one. The garbage collector patch is copied from amd64, the ucontext
defines simply have to use the correct sigcontext members, and for BoringSSL
we need to provide the setup function that tells BoringSSL which crypto accel
is supported by the CPU. For now this only enables NEON, which we have on all
OpenBSD/arm64 machines.
"makes sense, need to be sure it doesn't break existing working archs" sthen@
Tested by myself on arm64 by playing games/openra through iked(8) IPsec
Tested by myself on amd64 and i386
ok robert@ naddy@
no need to waste build time for now as build didn't complete
- on arm64, the generated binary segfaults
- on powerpc64, the build fails due to undefined symbols. gkoehler@
did the analyzis, and it seems that zig wants to IEEE quad floats
(which are missing for now on powerpc64)
* Disable the peephole optimizer on mips64 to avoid occasional crashes.
* Ensure sufficient alignment of builtin bytecode arrays so that
compiler.c can cast and access the data through struct ibf_header
without crashing (OpenBSD/mips64 requires strict alignment).
OK jeremy@
allows some additional debugging features for Python-based software
(for example there's a new "py-bt" command to print a Python backtrace
which can give clues if a py process is hanging).
ok rpointel@
The patch from https://www.lua.org/bugs.html#5.2.2-1 was backported and
applied to the wrong function (adjust_varargs() instead of luaD_precall()).
ok sthen
Some non-trivial adaptations:
* Remove -Wl,-z,notext from compiler flags
* Backport from ghc HEAD: move debugBelch into IF_DEBUG(linker)
* Move debugBelch into IF_DEBUG(linker) [fixup 3433]
* Undo ghci slowness [fixup 18727]
* Increase open FD limit for test runs to 1024
* Disable haddock on i386 using PFRAG
ok kili
to fix the build of 7.4 and 8.0 on sparc64, which otherwise fails
during configure because it cannot find several X11 libs that
libgd depends upon.
ok sthen
Zig is a general-purpose programming language and toolchain for
maintaining robust, optimal, and reusable software.
- Robust: behavior is correct even for edge cases such as out of memory.
- Optimal: write programs the best way they can behave and perform.
- Reusable: the same code works in many environments which have different constraints.
- Maintainable: precisely communicate intent to the compiler and other programmers. The language imposes a low overhead to reading code and is resilient to changing requirements and environments.
- use GH_* instead of DISTNAME/DISTFILES/MASTER_SITES
- use DPB_PROPERTIES=parallel
- build debug packages
- use py3 to build, disable python run dep
- remove bogus NO_CCACHE
- regen plist
