Re: llvm and Undefined symbols: ___truncsfbf2 problem
Thank you. I updated my current to recent current and confirmed that julia 1.11.0 beta1 builds and runs with the system clang (18.1.4). On Thu, 18 Apr 2024 00:36:28 +0200 Dimitry Andric wrote: > On 11 Apr 2024, at 15:07, Hiroo Ono wrote: > > > > Hello, > > > > I am trying to update the lang/julia port to 1.11.0 (currently > > still in beta 1). I seem to ran across this problem initially > > reported on MacOS. https://github.com/JuliaLang/julia/issues/52067 > > > > The llvm team seems to have patched this problem only for Darwin. > > https://github.com/llvm/llvm-project/pull/84192 > > > > I think the solution is also needed for FreeBSD, but should I > > report it directly to llvm team or report here or to FreeBSD > > bugzilla and ask toolchain maintainer of FreeBSD to report > > upstream? > > The __bf16 type is only available on some architectures, and only > supported by relatively recent compiler versions, in combination with > some runtime support (i.e. compiler-rt or libgcc). > > Approximately: it is available on aarch64, amd64, arm (with fp), i386 > (with sse2) and riscv. And it is supported by clang 15 and later > (though not for riscv, which requires clang 18), and gcc 13 and later. > > However, the runtime support in FreeBSD was only added with the recent > merge of llvm 18. The necessary library functions (truncdfbf2 and > truncsfbf2) are now in compiler-rt. > > -Dimitry > >
llvm and Undefined symbols: ___truncsfbf2 problem
Hello, I am trying to update the lang/julia port to 1.11.0 (currently still in beta 1). I seem to ran across this problem initially reported on MacOS. https://github.com/JuliaLang/julia/issues/52067 The llvm team seems to have patched this problem only for Darwin. https://github.com/llvm/llvm-project/pull/84192 I think the solution is also needed for FreeBSD, but should I report it directly to llvm team or report here or to FreeBSD bugzilla and ask toolchain maintainer of FreeBSD to report upstream? Hiroo Ono
Re: vinum error: statfs related?
At Sun, 16 Nov 2003 20:14:24 -0800 (PST), Daryl Chance wrote: I am currently not able to load my vinum array (haven't tried to revert back to pre-statfs source) Me too. After upgrading the kernel from -current as of mid september to today's, I rebooted and got vinum loaded, no drives found message. Rebooting with old kernel (and modules) brings back the vinum objects back again. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
lock order reversal
I've got a lock order reversal. #uname -a FreeBSD barleycoren.oikumene.gcd.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Sep 23 21:37:42 JST 2003 [EMAIL PROTECTED]:/build/usr/src/sys/BARLEYCOREN i386 Oct 11 18:14:53 barleycoren kernel: 1st 0xc082f060 system map (system map) @ /usr/src/sys/vm/vm_map.c:2236 Oct 11 18:14:53 barleycoren kernel: 2nd 0xc048e560 Giant (Giant) @ /usr/src/sys/vm/vm_map.c:2188 backtrace(c0418e40,c048e560,c0416343,c0416343,c0426bdd) at backtrace+0x17 witness_lock(c048e560,8,c0426bdd,88c,0) at witness_lock+0x5b6 _mtx_lock_flags(c048e560,0,c0426bdd,88c,c026cf6a) at _mtx_lock_flags+0x6a vm_map_delete(c082f000,dd839000,dd84a000,c456eb6c,c456eb6c) at vm_map_delete+0x1d6 vm_map_remove(c082f000,dd839000,dd84a000,dd547bd4,c029c970) at vm_map_remove+0x55 kmem_free(c082f000,dd839000,11000,c456eb6c,c456eb6c) at kmem_free+0x32 pipe_destroy_write_buffer(c456eb6c,0,c0419360,360,0) at pipe_destroy_write_buffer+0x60 pipe_direct_write(c456eb6c,dd547c80,c0419360,39c,c04b5be8) at pipe_direct_write+0x4e4 pipe_write(c456a000,dd547c80,c444e280,0,c424b5f0) at pipe_write+0x284 dofilewrite(c424b5f0,c456a000,1,80afb40,8000) at dofilewrite+0xe9 write(c424b5f0,dd547d14,c042b83f,3ec,3) at write+0x6e syscall(2f,2f,2f,80afb40,8000) at syscall+0x233 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (4), eip = 0x8050ec3, esp = 0xbfbfee8c, ebp = 0xbfbfeea8 --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install (stand/sysintsall) woes
As Makoto Matusita writes: $ Would you please try a newer (Nov/12/2001 or later) snapshot? clean install was necessary. I downloaded kern.flp and mfsroot.flp from november 9th, booted, started an ftp install. Eveything went smooth through newfs. Then three error messages appeared: Unable to mount /mnt/dev/ad0s1e on The current snapshot in the beginning of November failed to install because libdisk's function MakeDev() tried to mknod() in devfs partiton. The patch I provided just skipped mknod() if the kernel knew devfs, even if sysinstall tried to mknod() other than the devfs partition, which caused the bug you reported. Matusita-san has committed the proper fix to the problem, so please try newer snapshot and report the result as a followup to PR 31009 if possible. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
