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 target/87281] qsort checking ICE in ia64_reorg building libgo Date: Sat, 24 Jun 2023 09:45:53 +0000 [thread overview] Message-ID: <bug-87281-4-EwB8btJ9Hs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-87281-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87281 --- Comment #14 from Jan-Benedict Glaw <jbglaw@lug-owl.de> --- Still observable as of a8994014041: [...] ia64-linux-gcc -Wp,-MMD,kernel/.kallsyms.o.d -nostdinc -I./arch/ia64/include -I./arch/ia64/include/generated -I./include -I./arch/ia64/include/uapi -I./arch/ia64/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__ -DHAVE_WORKING_TEXT_ALIGN -DHAVE_MODEL_SMALL_ATTRIBUTE -DHAVE_SERIALIZE_DIRECTIVE -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Wno-format-security -funsigned-char -std=gnu11 -pipe -ffixed-r13 -mfixed-range=f12-f15,f32-f127 -frename-registers -fno-optimize-sibling-calls -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=2048 -fno-stack-protector -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 -falign-functions=32 -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -mconstant-gp -DKBUILD_MODFILE='"kernel/kallsyms"' -DKBUILD_BASENAME='"kallsyms"' -DKBUILD_MODNAME='"kallsyms"' -D__KBUILD_MODNAME=kmod_kallsyms -c -o kernel/kallsyms.o kernel/kallsyms.c kernel/kallsyms.c: In function 'kallsyms_lookup_names': kernel/kallsyms.c:268:1: error: qsort comparator non-negative on sorted output: 1 268 | } | ^ during RTL pass: mach kernel/kallsyms.c:268:1: internal compiler error: qsort checking failed 0x188b086 internal_error(char const*, ...) ???:0 0x18bf855 gcc_qsort(void*, unsigned long, unsigned long, int (*)(void const*, void const*)) ???:0 0x15c7a08 schedule_block(basic_block_def**, void*) ???:0 0x1685c1b schedule_ebb(rtx_insn*, rtx_insn*, bool) ???:0 0x168622d schedule_ebbs() ???:0 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. make[2]: *** [scripts/Makefile.build:252: kernel/kallsyms.o] Error 1 make[1]: *** [scripts/Makefile.build:494: kernel] Error 2 make: *** [Makefile:2026: .] Error 2
next prev parent reply other threads:[~2023-06-24 9:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-87281-4@http.gcc.gnu.org/bugzilla/> 2022-08-14 19:08 ` pinskia at gcc dot gnu.org 2022-08-14 19:58 ` slyfox at gcc dot gnu.org 2022-12-20 22:21 ` jbglaw@lug-owl.de 2023-06-24 9:45 ` jbglaw@lug-owl.de [this message] 2023-11-02 22:36 ` jsm28 at gcc dot gnu.org 2023-11-02 22:38 ` [Bug target/87281] [14 Regression] " jsm28 at gcc dot gnu.org 2024-01-10 10:12 ` rguenth at gcc dot gnu.org 2024-05-07 7:39 ` [Bug target/87281] [14/15 " rguenth 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-87281-4-EwB8btJ9Hs@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).