# git rev-parse -q --verify 227c3e9eb5cf3552c2cc83225df6d14adb05f8e8^{commit} 227c3e9eb5cf3552c2cc83225df6d14adb05f8e8 already have revision, skipping fetch # git checkout -q -f -B kisskb 227c3e9eb5cf3552c2cc83225df6d14adb05f8e8 # git clean -qxdf # < git log -1 # commit 227c3e9eb5cf3552c2cc83225df6d14adb05f8e8 # Merge: 56c631f5aec3 32ee8230b2b0 # Author: Linus Torvalds # Date: Sat Sep 21 09:47:19 2019 -0700 # # Merge tag 'compiler-attributes-for-linus-v5.4' of git://github.com/ojeda/linux # # Pull asm inline support from Miguel Ojeda: # "Make use of gcc 9's "asm inline()" (Rasmus Villemoes): # # gcc 9+ (and gcc 8.3, 7.5) provides a way to override the otherwise # crude heuristic that gcc uses to estimate the size of the code # represented by an asm() statement. From the gcc docs # # If you use 'asm inline' instead of just 'asm', then for inlining # purposes the size of the asm is taken as the minimum size, ignoring # how many instructions GCC thinks it is. # # For compatibility with older compilers, we obviously want a # # #if [understands asm inline] # #define asm_inline asm inline # #else # #define asm_inline asm # #endif # # But since we #define the identifier inline to attach some attributes, # we have to use an alternate spelling of that keyword. gcc provides # both __inline__ and __inline, and we currently #define both to inline, # so they all have the same semantics. # # We have to free up one of __inline__ and __inline, and the latter is # by far the easiest. # # The two x86 changes cause smaller code gen differences than I'd # expect, but I think we do want the asm_inline thing available sooner # or later, so this is just to get the ball rolling" # # * tag 'compiler-attributes-for-linus-v5.4' of git://github.com/ojeda/linux: # x86: bug.h: use asm_inline in _BUG_FLAGS definitions # x86: alternative.h: use asm_inline for all alternative variants # compiler-types.h: add asm_inline definition # compiler_types.h: don't #define __inline # lib/zstd/mem.h: replace __inline by inline # staging: rtl8723bs: replace __inline by inline # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 227c3e9eb5cf3552c2cc83225df6d14adb05f8e8 # < make -s -j 48 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- ppc64le_defconfig # make -s -j 48 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- WARNING: vmlinux.o(.text+0x31e4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() The function __boot_from_prom() references the function __init prom_init(). This is often because __boot_from_prom lacks a __init annotation or the annotation of prom_init is wrong. WARNING: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Completed OK # rm -rf /kisskb/build/linus_ppc64le_defconfig_ppc64le-gcc5 # Build took: 0:02:46.818598