Date: Fri, 09 Jul 2021 16:47:31 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257085] lang/racket: update to 8.1 Message-ID: <bug-257085-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257085 Bug ID: 257085 Summary: lang/racket: update to 8.1 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: olgeni@FreeBSD.org Reporter: bsd@philippost.de Flags: maintainer-feedback?(olgeni@FreeBSD.org) Assignee: olgeni@FreeBSD.org This patch updates lang/racket to version 8.1. With Racket 8.0, the default backend was switched to an implementation base= d on Chez Scheme. The old byte code interpreter is still supported. The patch introduces two options -- BC and CS. I made them mutually exclusi= ve, even though Racket supports building and installing both backends simultaneously. The CS backend is enabled by default. The --enable-libffi and --enable-places options where added to BC_CONFIGURE= _ON. The CS backend configure script does not provide these options. Racket claims to support the Chez Scheme backend on i386, amd64, armv6, aar= ch64 and powerpc (https://github.com/racket/racket/blob/master/racket/src/ChezScheme/README.= md) on FreeBSD, but only amd64 and i386 seem to have machine types defined. I c= ould not test if the CS backend works on architectures other than amd64 and i386= , or which machine types the configure script chooses there. According to the Racket documentation, JIT compilation is supported on 32 b= it PowerPC (c.f. https://docs.racket-lang.org/guide/performance.html#%28part._.J.I.T%29). I carried over the patch to src/bc/sconfig.h since I do not have access to FreeBSD machines with architectures other than amd64 and i386. This patch is based on the work by 'm.ne' in Bug 255529. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257085-7788>