Skip site navigation (1)Skip section navigation (2)


2016/freebsd-toolchain/20161204.freebsd-toolchain

Messages: 41, new messages first
Last update: Mon Feb 13 14:24:36 2023

home | archive sorted by: subject | author | date | reverse date
  1. Dec  3 bugzilla-noreply@freebsd.o [Bug 214902] head -r309179 buildworld on powerpc64 via clang 3.9.0: llvm::sys::CompareAndSwap and llvm::sys::MemoryFence undefined so build st
  2. Dec  3 bugzilla-noreply@freebsd.o [Bug 214902] head -r309179 buildworld on powerpc64 via clang 3.9.0: llvm::sys::CompareAndSwap and llvm::sys::MemoryFence undefined so build st
  3. Dec  3 Mark Millard               Re: Cross built head -r309179 TARGET_ARCH=powerpc64 with clang 3.9.0/powerpc64-binutils based buildworld operates; but fails "self-hosted buil
  4. Dec  3 Kevin Bowling              Re: Cross built head -r309179 TARGET_ARCH=powerpc64 with clang 3.9.0/powerpc64-binutils based buildworld operates; but fails "self-hosted buil
  5. Dec  2 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
  6. Dec  2 David Chisnall             Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
  7. Dec  2 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
  8. Dec  2 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
  9. Dec  1 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference
 10. Dec  1 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
 11. Dec  1 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
 12. Dec  1 Mark Millard               Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
 13. Nov 30 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference
 14. Nov 30 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference
 15. Nov 29 Ed Maste                   Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required f
 16. Nov 29 Mark Millard               WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required for C
 17. Nov 29 Konstantin Belousov        Re: How to turn off SSP stack-protector on 11.0S
 18. Nov 29 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference
 19. Nov 29 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference
 20. Nov 28 bugzilla-noreply@freebsd.o [Bug 214902] head -r309179 buildworld on powerpc64 via clang 3.9.0: llvm::sys::CompareAndSwap and llvm::sys::MemoryFence undefined so build st


21. Nov 28 bugzilla-noreply@freebsd.o [Bug 214902] head -r309179 buildworld on powerpc64 via clang 3.9.0: llvm::sys::CompareAndSwap and llvm::sys::MemoryFence undefined so build st 22. Nov 28 bugzilla-noreply@freebsd.o [Bug 214902] head -r309179 buildworld on powerpc64 via clang 3.9.0: llvm::sys::CompareAndSwap and llvm::sys::MemoryFence undefined so build st 23. Nov 28 bugzilla-noreply@freebsd.o [Bug 214903] head -r309179 clang 3.9.0 TARGET_ARCH=powerpc64 cross built buildkernel stops for: converts between pointers to integer types wit 24. Nov 28 bugzilla-noreply@freebsd.o [Bug 214904] head -r309179 clang 3.9.0 TARGET_ARCH=powerpc64 cross-built buildkernel stops for: rejected assembler notation 25. Nov 28 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference 26. Nov 28 bugzilla-noreply@freebsd.o [Bug 193594] stddef.h should define max_align_t 27. Nov 28 Mark Millard head -r309179 clang 3.9.0 TARGET_ARCH=powerpc64 cross-built buildkernel stops for: rejected assembler notation 28. Nov 28 bugzilla-noreply@freebsd.o [Bug 214862] head -r309179 clang 3.9.0 vs. TARGET_ARCH=powerpc: fsck_ufs and "df -m" are example failures: __floatdidf gets SIGSEGV's in both 29. Nov 28 Mark Millard Cross built head -r309179 TARGET_ARCH=powerpc64 with clang 3.9.0/powerpc64-binutils based buildworld operates; but fails "self-hosted buildwor 30. Nov 28 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference 31. Nov 28 Mark Millard Re: WITH_CLANG_BOOTSTRAP= for TARGET_ARCH=powerpc64 but bound to devel/powerpc64-binutils : can such be done? 32. Nov 28 Mark Millard head -r309179 clang 3.9.0 for TARGET_ARCH=powerpc64 with devel/powerpc64-binutils used: WITH_LIB32= related assembler source rejected. . . 33. Nov 28 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference 34. Nov 28 Mark Millard WITH_CLANG_BOOTSTRAP= for TARGET_ARCH=powerpc64 but bound to devel/powerpc64-binutils : can such be done? 35. Nov 27 bugzilla-noreply@freebsd.o [Bug 214855] head -r309179 TARGET_ARCH=powerpc64 clang 3.9.0 based cross build: powerpc.powerpc64/usr/src/tmp/usr/bin/ld: BFD 2.17.50 [FreeBSD 36. Nov 27 bugzilla-noreply@freebsd.o [Bug 214862] head -r309197 clang 3.9.0 vs. TARGET_ARCH=powerpc: fsck_ufs and "df -m" are example failures: __floatdidf gets SIGSEGV's in both 37. Nov 27 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference 38. Nov 27 Mark Millard Re: clang 3.9.0 vs. TARGET_ARCH=powerpc: fsck_ufs and "df -m" are example failures: __floatdidf gets SIGSEGV's in both of them. [Code generati 39. Nov 27 Mark Millard Re: clang 3.9.0 vs. TARGET_ARCH=powerpc: fsck_ufs and "df -m" are example failures: __floatdidf gets SIGSEGV's in both of them. 40. Nov 27 Mark Millard Re: clang 3.9.0 vs. TARGET_ARCH=powerpc: fsck_ufs and "df -m" are example failures: __floatdidf gets SIGSEGV's in both of them.
41. Nov 27 bugzilla-noreply@freebsd.o [Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference


home | archive sorted by: subject | author | date | reverse date