{"push_id":2727978014,"size":9,"distinct_size":9,"ref":"refs/heads/bleeding-edge","head":"e3b6e0e22254288fbdb094bc852787d68d07ae16","before":"ace5fb2017e4e1616540c9a68b8aadbdd9192cda","commits":[{"sha":"ab196e4c91711dc96b7279c7d5efa301baa1a2ee","author":{"name":"Alexey Brodkin","email":"df74735e5e8e4da139876d19d7450f461d604b9f@synopsys.com"},"message":"package/gcc: Backport code generation fix for ARC700\n\nFixes assembler failure when compiling for ARC700 only:\n------------------------>8---------------------\n{standard input}: Assembler messages:\n{standard input}:213: Error: operand out of range (128 is not between -128 and 127)\nmake[2]: *** [scripts/Makefile.build:317: net/ipv4/xfrm4_mode_tunnel.o] Error 1\n------------------------>8---------------------\n\nThis is an upstream fix scheduled for the next release, see\nhttps://github.com/gcc-mirror/gcc/commit/5afc07eeb18fb7dd351ac981367bce721ca22af3\n\nSigned-off-by: Alexey Brodkin <abrodkin@synopsys.com>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\n\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/ab196e4c91711dc96b7279c7d5efa301baa1a2ee"},{"sha":"b35ad5d0b45e5288f4019aeaa06b87ef0f2ef016","author":{"name":"Hollis Blanchard","email":"cd9c751a7d90e05d28d5b07e1a27ef2eba49db0a@mentor.com"},"message":"ncurses: make host-ncurses use host terminfo\n\nHost GDB suffers a serious problem: pressing backspace (or ^W ^U or any other\n\"delete\" key) results in a plain space being printed instead, making the\ncommand prompt almost completely unusable.\n\nThat's because it's using host-ncurses, which embeds a path for the terminfo\ndatabase into the library itself. That path ends up being something like\n/home/hollisb/buildroot.git/output/host/share/terminfo, which obviously doesn't\ngenerally exist other hosts. ('relocate-sdk.sh' cannot and does not edit\nbinaries like libncurses.so.6, so doesn't resolve this problem.)\n\n/usr/share/terminfo is a far better path to use, since it almost certainly\nexists on the host. Theoretically, it could be from a different ncurses version\nwith incompatible terminfo database format, but this doesn't seem to be a\nproblem in practice. (Future patches could address the theoretical problem if\nit actually appears in real life.)\n\nThis change allows buildroot's host gdb, which uses ncurses 6.x, to work on\nRHEL5, RHEL6, and RHEL7, which all provide terminfo from ncurses 5.x.\n\nSigned-off-by: Hollis Blanchard <hollis_blanchard@mentor.com>\nReviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/b35ad5d0b45e5288f4019aeaa06b87ef0f2ef016"},{"sha":"be696b3571f875963f595ee94b7f851c9e79e39f","author":{"name":"Thomas Petazzoni","email":"a5d87d2bd7c424ee5cbdb4e978635bf653d5a005@free-electrons.com"},"message":"gcc: tweak SH4 multilib list\n\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/be696b3571f875963f595ee94b7f851c9e79e39f"},{"sha":"088f31f37545e29cc6acf6e63923814a0ce14ef0","author":{"name":"Romain Naour","email":"48b9fcabb497dca2879ac6d9e447e6704661c558@gmail.com"},"message":"linux: disable attribute alias with gcc >= 8.1\n\ngcc-8 started warning about function aliases that have a non-matching\nprototype. This seems rather useful in general, but it causes tons of\nwarnings in the Linux kernel, where we rely on abusing those aliases\nfor system call entry points, in order to sanitze the arguments passed\nfrom user space in registers.\n\nSee https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82435\n\nSigned-off-by: Romain Naour <romain.naour@gmail.com>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/088f31f37545e29cc6acf6e63923814a0ce14ef0"},{"sha":"431ad502fa3d21206c4f72af865ac6478d618313","author":{"name":"Thomas Petazzoni","email":"a5d87d2bd7c424ee5cbdb4e978635bf653d5a005@bootlin.com"},"message":"configs/qemu_ppc64*_pseries: backport upstream Linux kernel patch\n\nThe backported patch is needed for the kernel to build with GCC 8.x.\n\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/431ad502fa3d21206c4f72af865ac6478d618313"},{"sha":"bb860dd949b2b4f8c28a4fc7e16f52e97b2d6fbb","author":{"name":"Romain Naour","email":"48b9fcabb497dca2879ac6d9e447e6704661c558@gmail.com"},"message":"SSP: disable ssp support on microblaze\n\nAs reported by [1], SSP support is missing in the Buildroot toolchain\nfor microblaze even if it's requested by selecting\nBR2_TOOLCHAIN_HAS_SSP config option.\n\nIn Buildroot, we are using libssp provided by the C library (Glibc,\nmusl, uClibc-ng) when available. We are not using libssp from gcc.\n\nSo for a microblaze glibc based toolchain, the SSP support is enabled\nunconditionally by a select BR2_TOOLCHAIN_HAS_SSP.\n\nBR2_microblazeel=y\nBR2_TOOLCHAIN_BUILDROOT_GLIBC=y\nBR2_KERNEL_HEADERS_4_14=y\nBR2_BINUTILS_VERSION_2_30_X=y\nBR2_GCC_VERSION_8_X=y\nBR2_TOOLCHAIN_BUILDROOT_CXX=y\n\nWhile building the toolchain, we are building host-binutils which\nprovide \"as\" (assembler) and host-gcc-initial wich provide a\nminimal cross gcc (C only cross-compiler without any C library).\nWhen SSP support is requested, gcc_cv_libc_provides_ssp=yes is\nadded to the make command line (see [2] for full details)\n\nWith this setting, the SSP support is requested but it's not available\nin the end and the toochain build succeed.\n\nWhen the microblaze toolchain is imported to Biuldroot (2018.05) as\nexternal toolchain with BR2_TOOLCHAIN_EXTERNAL_HAS_SSP set, the build\nstop with :\n\"SSP support not available in this toolchain, please disable BR2_TOOLCHAIN_EXTERNAL_HAS_SSP\"\n\nThe test is doing the following command line:\n\necho 'void main(){}' | [...]/host/bin/microblazeel-linux-gcc.br_real -Werror -fstack-protector -x c - -o [...]/build/.br-toolchain-test.tmp\ncc1: error: -fstack-protector not supported for this target [-Werror]\n\nWhen we look at the gcc-final log file (config.log) we can see this\nerror several time when using the minimal gcc (from host-gcc-initial).\nSo Why the minimal gcc doesn't support SSP?\n\nWhen we look at the gcc-initial log file (config.log) we can see an\nerror with 'as':\n\nconfigure:23194: checking assembler for cfi directives\nconfigure:23209: [...]microblazeel-buildroot-linux-gnu/bin/as    -o conftest.o conftest.s >&5\nconftest.s: Assembler messages:\nconftest.s:2: Error: CFI is not supported for this target\nconftest.s:3: Error: CFI is not supported for this target\nconftest.s:4: Error: CFI is not supported for this target\nconftest.s:5: Error: CFI is not supported for this target\nconftest.s:6: Error: CFI is not supported for this target\nconftest.s:7: Error: CFI is not supported for this target\nconfigure:23212: $? = 1\nconfigure: failed program was\n    .text\n    .cfi_startproc\n    .cfi_offset 0, 0\n    .cfi_same_value 1\n    .cfi_def_cfa 1, 2\n    .cfi_escape 1, 2, 3, 4, 5\n    .cfi_endproc\n\nThis is the only relevant difference compared to a nios2 toolchain where\nlibssp is enabled and available (nios2 is an example).\n\n\"CFI\" stand for \"Control Flow Integrity\" and it seems that SSP support\nrequires CFI target support (see [3] for some explanation).\n\nThe SSP support seems to depends on CFI support, but the toolchain\ninfrastructure is not detailed enough to handle the CFI dependency.\n\nIn the other hand, microblaze is the only architecture where CFI support\nis missing.\n\nDisable SSP support for microblaze entirely.\n\nFixes:\nhttps://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006389\n\n[1] https://gitlab.com/free-electrons/toolchains-builder/issues/1\n[2] https://git.buildroot.net/buildroot/tree/package/gcc/gcc.mk?h=2018.05#n275\n[3] https://grsecurity.net/rap_faq.php\n\nSigned-off-by: Romain Naour <romain.naour@gmail.com>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/bb860dd949b2b4f8c28a4fc7e16f52e97b2d6fbb"},{"sha":"bd343d5e1c1f2b30fd709ad44ba0f5b286000028","author":{"name":"Romain Naour","email":"48b9fcabb497dca2879ac6d9e447e6704661c558@gmail.com"},"message":"qemu/sh4-r2d: restore the old sh-sci driver behaviour\n\nThis reverts commit 18e8cf159177100e69d528293f8cf6875c0b1bca (kernel)\n\nThe last Qemu kernel update [1] introduced a regresion in sh4 SCIF\nserial device. Some keyboard presses are very slow to be taken into\naccount, perhaps not even taken into account at all. This would\nexplain why our test infrastructure doesn’t manage to login as root\n[2][3][4].\n\ngit bisect reported a kernel patch from 4.11, increasing RX FIFO\ntrigger defaults value for sh-sci (H)SCIF. The kernel patch itself\nlooks good but the Qemu emulation is not ready to handle this new\nsetting.\n\n>From Qemu (2.12.0): target/sh4/README.sh4\n\"Configuration of the second serial port (SCIF) is supported. FIFO\nhandling infrastructure has been started but is not completed yet.\"\n\nWe can't use the first serial port (ttySC0) because it's the second\nSH UART that's emulated by Qemu.\n\nIn order to be able to test sh4 architecture with newer kernel,\nrevert to the old behaviour.\n\n[1] 03fb00f2175cdb4565e26fcb9b3da1c1059de1bd\n[2] https://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006425\n[3] https://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006427\n[4] https://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006426\n\nSigned-off-by: Romain Naour <romain.naour@gmail.com>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/bd343d5e1c1f2b30fd709ad44ba0f5b286000028"},{"sha":"f103e8ec788ad5c1551f9f6a1a24f1b287edf32d","author":{"name":"Romain Naour","email":"48b9fcabb497dca2879ac6d9e447e6704661c558@gmail.com"},"message":"qemu/sh4eb-r2d: restore the old sh-sci driver behaviour\n\nAs for sh4-r2d (little-endian) restore the old sh-sci driver behaviour\nfor sh4eb-r2d.\n\nTested with qemu_sh4eb_r2d_defconfig.\n\nSigned-off-by: Romain Naour <romain.naour@gmail.com>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/f103e8ec788ad5c1551f9f6a1a24f1b287edf32d"},{"sha":"e3b6e0e22254288fbdb094bc852787d68d07ae16","author":{"name":"Romain Naour","email":"48b9fcabb497dca2879ac6d9e447e6704661c558@smile.fr"},"message":"package/elf2flt: fix build with Binutils >= 2.31\n\nBinutils added diagnostics.h to bfd.h [1], so elf2flt must create a\nsymlink for this header.\n\nFixes:\nhttps://gitlab.com/free-electrons/toolchains-builder/-/jobs/82284139\n\n[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=95da9854466ada2572b42f5528711a06a2d42db1\n\nSigned-off-by: Romain Naour <romain.naour@smile.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Peter Korsgaard <peter@korsgaard.com>","distinct":true,"url":"https://api.github.com/repos/bootlin/buildroot-toolchains/commits/e3b6e0e22254288fbdb094bc852787d68d07ae16"}]}
{"actor":{"display_login":"tpetazzoni"}}