toolchain  

Messages by Thread

• • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
  • [Bug 264094] VNET and DPCPU defined in modules panic on use on arm64 after LLVM 14 import due to new linker relaxation bugzilla-noreply
• [Bug 268319] LTO fails on the port cad/nvc on i386: undefined symbol: _GLOBAL_OFFSET_TABLE_, see error: undefined symbol: _GLOBAL_OFFSET_TABLE_ bugzilla-noreply
  • [Bug 268319] LTO fails on the port cad/nvc on i386: undefined symbol: _GLOBAL_OFFSET_TABLE_, see error: undefined symbol: _GLOBAL_OFFSET_TABLE_ bugzilla-noreply
• [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
  • [Bug 268021] Many port builds run out of memory on armv7 bugzilla-noreply
• [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
  • [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
  • [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
  • [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
  • [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
  • [Bug 268019] clang Assertion failed on devel/libdispatch bugzilla-noreply
• [Bug 268009] clang crashes on armv7 on the port math/py-z3-solver bugzilla-noreply
  • [Bug 268009] clang crashes on armv7 on the port math/py-z3-solver bugzilla-noreply
• [Bug 265809] clang never finishes on one particular C++ file (for science/psi4) bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file (for science/psi4) bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file (for science/psi4) bugzilla-noreply
• [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
  • [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
• [Bug 267751] lang/gcc11: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list bugzilla-noreply
• [Bug 267768] Simple OpenMP example crashes with thread sanitizer (-fsanitize=thread) bugzilla-noreply
  • [Bug 267768] Simple OpenMP example crashes with thread sanitizer (-fsanitize=thread) bugzilla-noreply
• maintainer-feedback requested: [Bug 267179] Included LLDB broken bugzilla-noreply
• [Bug 267179] Included LLDB broken bugzilla-noreply
  • [Bug 267179] Included LLDB broken bugzilla-noreply
  • [Bug 267179] Included LLDB broken bugzilla-noreply
  • [Bug 267179] Included LLDB broken bugzilla-noreply
• [Bug 266834] clang: search doesn't work for filesystem::path in clang-14 bugzilla-noreply
  • [Bug 266834] clang: search doesn't work for filesystem::path in clang-14 bugzilla-noreply
• [Bug 266834] clang: search doesn't work for filesystem::path in version bugzilla-noreply
• [Bug 266777] c++ crashes during link on arm64 on math/lean bugzilla-noreply
• [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
  • [Bug 234232] clang Assertion failed when building the port devel/aws-checksums bugzilla-noreply
• devel/freebsd-binutils@* conflicts with system toolchain for * matching the system: needs at least a devel/freebsd-binutils@* installation warning if the conflict is not removed Mark Millard
• [Bug 266402] clang crashes on math/lean on aarch64 on 13.1-RELEASE and 14-CURRENT bugzilla-noreply
  • [Bug 266402] clang crashes on math/lean on aarch64 on 13.1-RELEASE and 14-CURRENT bugzilla-noreply
  • [Bug 266402] clang crashes on math/lean on aarch64 on 13.1-RELEASE and 14-CURRENT bugzilla-noreply
• [Bug 266402] clang crashes on math/lean on amd64 on 13.1-RELEASE and 14-CURRENT bugzilla-noreply
• [Bug 241773] lldb does not display external variables properly. bugzilla-noreply
  • [Bug 241773] lldb does not display external variables properly. bugzilla-noreply
  • [Bug 241773] lldb does not display external variables properly. bugzilla-noreply
  • [Bug 241773] lldb does not display external variables properly. bugzilla-noreply
• lang/gcc12 's g++12 gets a failure on aarch64 FreeBSD (main) but not on aarch64 Fedora (36), small test case Mark Millard
  • Re: lang/gcc12 's g++12 gets a failure on aarch64 FreeBSD (main) but not on aarch64 Fedora (36), small test case Mark Millard
• [Bug 266146] Clang prints bogus warning: incompatible pointer types passing 'struct kinfo_proc *' to parameter of type 'struct kinfo_proc *' [-Wincompatible-pointer-types] bugzilla-noreply
  • [Bug 266146] Clang prints bogus warning: incompatible pointer types passing 'struct kinfo_proc *' to parameter of type 'struct kinfo_proc *' [-Wincompatible-pointer-types] bugzilla-noreply
  • [Bug 266146] Clang prints bogus warning: incompatible pointer types passing 'struct kinfo_proc *' to parameter of type 'struct kinfo_proc *' [-Wincompatible-pointer-types] bugzilla-noreply
  • [Bug 266146] Clang prints bogus warning: incompatible pointer types passing 'struct kinfo_proc *' to parameter of type 'struct kinfo_proc *' [-Wincompatible-pointer-types] bugzilla-noreply
• /usr/local/bin/aarch64-unknown-freebsd14.0-ld vs. system the system toolchain on aarch64 [example]: when found, lld is not used by default Mark Millard
• FYI: armv7-direct-boot vs. armv7-under-aarch64-boot process size limitations: they are different Mark Millard
• Reduced reproduction of games/libretro-beetle_psx 's armv7 build failure Mark Millard
  • Re: Reduced reproduction of games/libretro-beetle_psx 's armv7 build failure Mark Millard
• [Bug 265962] lang/gcc11: expose non-default -stdlib=libc++ support bugzilla-noreply
  • maintainer-feedback requested: [Bug 265962] lang/gcc11: expose non-default -stdlib=libc++ support bugzilla-noreply
  • [Bug 265962] lang/gcc11: expose non-default -stdlib=libc++ support bugzilla-noreply
  • [Bug 265962] lang/gcc11: expose non-default -stdlib=libc++ support bugzilla-noreply
• [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
  • [Bug 265949] llvm prints warnings like: The function '%142 = OpFunction %7 None %134' could not be inlined because the return instruction is not at the end of the function. This could be fixed by running merge-return before inlining. bugzilla-noreply
• [package - 123amd64-default][lang/gcc12] Failed for gcc12-12.1.0 in build pkg-fallout
• [package - 130i386-default][lang/gcc12] Failed for gcc12-12.1.0 in build pkg-fallout
• [Bug 265826] clang crashes on cad/nvc on 14/i386 bugzilla-noreply
  • [Bug 265826] clang crashes on cad/nvc on 14/i386 bugzilla-noreply
  • [Bug 265826] clang crashes on cad/nvc on 14/i386 bugzilla-noreply
• [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
  • [Bug 265809] clang never finishes on one particular C++ file bugzilla-noreply
• FYI: libclang so-numbers: "This partially reverts c7b3a91", now considered fixed and closed Mark Millard
• [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
  • [Bug 265758] clang crashes on math/py-fastcluster on 14/amd64 bugzilla-noreply
• [Bug 265757] clang crashes on devel/rubygem-aws-crt on 14/amd64 bugzilla-noreply
  • [Bug 265757] clang crashes on devel/rubygem-aws-crt on 14/amd64 bugzilla-noreply
  • [Bug 265757] clang crashes on devel/rubygem-aws-crt on 14/amd64 bugzilla-noreply
  • [Bug 265757] clang crashes on devel/rubygem-aws-crt on 14/amd64 bugzilla-noreply
  • [Bug 265757] clang crashes on devel/rubygem-aws-crt on 14/amd64 bugzilla-noreply
• [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
  • [Bug 265756] clang crashes on devel/py-awscrt on amd64 on 14 bugzilla-noreply
• [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
  • [Bug 265755] clang crashes on math/octave-forge-interval on amd64 on 14 bugzilla-noreply
• [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386, amd64 on 14 bugzilla-noreply
• [Bug 265751] clang crashes on science/py-tweedledum on i386 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386 bugzilla-noreply
  • [Bug 265751] clang crashes on science/py-tweedledum on i386 bugzilla-noreply
• [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply
  • [Bug 265723] clang crashes on many ports bugzilla-noreply

• Earlier messages
• Later messages