public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbglaw@lug-owl.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/107997] New: fd8dd6c03849691 probably uncovered an issue building the Linux kernel Date: Tue, 06 Dec 2022 22:24:13 +0000 [thread overview] Message-ID: <bug-107997-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107997 Bug ID: 107997 Summary: fd8dd6c03849691 probably uncovered an issue building the Linux kernel Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: regression Assignee: unassigned at gcc dot gnu.org Reporter: jbglaw@lug-owl.de Target Milestone: --- Hi! Starting with commit fd8dd6c0384969170e594be34da278a072d5eb76, I see Linux kernel build errors for the skiroot_defconfig: [mk all 2022-12-05 19:50:10] powerpc64-linux-gcc -Wp,-MMD,drivers/dma-buf/.dma-fence-array.o.d -nostdinc -I./arch/powerpc/include -I./arch/powerpc/include/generated -I./include -I./arch/po werpc/include/uapi -I./arch/powerpc/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -I ./arch/powerpc -DHAVE_AS_ATHIGH=1 -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-comm on -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Wno-format-security -std=gnu11 -mlittle-endian -m64 -msoft-float -pipe -mtraceback=no -mabi=elfv2 -mcmodel=medium -mno-pointers-to-nested-functions -mcpu=power8 -mtune=power10 -mno-prefixed -mno-pcrel -mno-altivec -mno-vsx -mno-mma -fno-asynchronous-unwind-tables -mno-string -Wa,-maltivec -Wa,-mpower4 -Wa,-many -mno-strict-align -mlittle-endian -mstack-protector-guard=tls -mstack-protector-guard-reg=r13 -fno-delete-null-pointer-checks -Wno-frame-address -Wno-form at-truncation -Wno-format-overflow -Wno-address-of-packed-member -Os -fno-allow-store-data-races -Wframe-larger-than=2048 -fstack-protector-strong -Wno-main -Wno-unused-but-set-variable -Wno- unused-const-variable -Wno-dangling-pointer -fomit-frame-pointer -ftrivial-auto-var-init=zero -fno-stack-clash-protection -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wcast-function -type -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow -fno-stack-check -fconse rve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -mstack-protector-guard-offset=2800 -DKBUILD_MODFILE='"drivers/dma-buf/dma-fe nce-array"' -DKBUILD_BASENAME='"dma_fence_array"' -DKBUILD_MODNAME='"dma_fence_array"' -D__KBUILD_MODNAME=kmod_dma_fence_array -c -o drivers/dma-buf/dma-fence-array.o drivers/dma-buf/dma-fenc e-array.c [mk all 2022-12-05 19:50:10] drivers/dma-buf/dma-fence-array.c: In function 'dma_fence_array_create': [mk all 2022-12-05 19:50:10] drivers/dma-buf/dma-fence-array.c:154:25: error: control flow in the middle of basic block 12 [mk all 2022-12-05 19:50:10] 154 | struct dma_fence_array *dma_fence_array_create(int num_fences, [mk all 2022-12-05 19:50:10] | ^~~~~~~~~~~~~~~~~~~~~~ [mk all 2022-12-05 19:50:10] during GIMPLE pass: ivopts [mk all 2022-12-05 19:50:10] drivers/dma-buf/dma-fence-array.c:154:25: internal compiler error: verify_flow_info failed [mk all 2022-12-05 19:50:10] 0x19ea876 internal_error(char const*, ...) [mk all 2022-12-05 19:50:10] ???:0 [mk all 2022-12-05 19:50:10] 0x94b00e verify_flow_info() [mk all 2022-12-05 19:50:10] ???:0 [mk all 2022-12-05 19:50:10] Please submit a full bug report, with preprocessed source (by using -freport-bug). [mk all 2022-12-05 19:50:10] Please include the complete backtrace with any bug report. [mk all 2022-12-05 19:50:10] See <https://gcc.gnu.org/bugs/> for instructions. (Cf. https://gcc.gnu.org/pipermail/gcc-patches/2022-December/607874.html) I'll add the preprocessed sources.
next reply other threads:[~2022-12-06 22:24 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 22:24 jbglaw@lug-owl.de [this message] 2022-12-07 0:08 ` [Bug tree-optimization/107997] [13 Regression] " pinskia at gcc dot gnu.org 2022-12-08 17:41 ` [Bug tree-optimization/107997] [13 Regression] r13-4389-gfd8dd6c0384969 " jakub at gcc dot gnu.org 2022-12-08 18:07 ` jbglaw@lug-owl.de 2022-12-08 18:47 ` jbglaw@lug-owl.de 2022-12-08 18:47 ` jbglaw@lug-owl.de 2022-12-08 18:55 ` jakub at gcc dot gnu.org 2022-12-08 19:18 ` jakub at gcc dot gnu.org 2022-12-08 19:22 ` [Bug tree-optimization/107997] [10/11/12/13 " pinskia at gcc dot gnu.org 2022-12-08 19:50 ` jakub at gcc dot gnu.org 2022-12-09 13:49 ` jakub at gcc dot gnu.org 2022-12-09 18:27 ` jbglaw@lug-owl.de 2022-12-10 15:51 ` cvs-commit at gcc dot gnu.org 2022-12-14 10:33 ` jbglaw@lug-owl.de 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:58 ` jakub at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 9:33 ` jakub at gcc dot gnu.org 2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:22 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107997-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).