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 rtl-optimization/84345] [10/11/12/13 Regression] ICE: qsort checking failed (error: qsort comparator non-negative on sorted output: 1)
Date: Tue, 20 Dec 2022 13:16:41 +0000 [thread overview]
Message-ID: <bug-84345-4-ZYPkkGlEJF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84345-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84345
Jan-Benedict Glaw <jbglaw@lug-owl.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbglaw@lug-owl.de
--- Comment #17 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
Just found this issue with GCC 13 (g:2dc5d6b1e7e) building the Linux kernel for
ia64 (--target=ia64-linux, with eg. the zx1_defconfig):
[mk all 2022-12-20 12:06:38] 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-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
[mk all 2022-12-20 12:06:40] kernel/kallsyms.c: In function
'kallsyms_lookup_names':
[mk all 2022-12-20 12:06:40] kernel/kallsyms.c:268:1: error: qsort comparator
non-negative on sorted output: 7
[mk all 2022-12-20 12:06:40] 268 | }
[mk all 2022-12-20 12:06:40] | ^
[mk all 2022-12-20 12:06:40] during RTL pass: mach
[mk all 2022-12-20 12:06:40] kernel/kallsyms.c:268:1: internal compiler error:
qsort checking failed
[mk all 2022-12-20 12:06:40] 0x17f0fa6 internal_error(char const*, ...)
[mk all 2022-12-20 12:06:40] ???:0
[mk all 2022-12-20 12:06:40] 0x1823ee5 gcc_qsort(void*, unsigned long, unsigned
long, int (*)(void const*, void const*))
[mk all 2022-12-20 12:06:40] ???:0
[mk all 2022-12-20 12:06:40] 0x163c9a7 schedule_block(basic_block_def**, void*)
[mk all 2022-12-20 12:06:40] ???:0
[mk all 2022-12-20 12:06:40] 0x171beb0 schedule_ebb(rtx_insn*, rtx_insn*, bool)
[mk all 2022-12-20 12:06:40] ???:0
[mk all 2022-12-20 12:06:40] 0x171c4a9 schedule_ebbs()
[mk all 2022-12-20 12:06:40] ???:0
[mk all 2022-12-20 12:06:40] Please submit a full bug report, with preprocessed
source (by using -freport-bug).
[mk all 2022-12-20 12:06:40] Please include the complete backtrace with any bug
report.
[mk all 2022-12-20 12:06:40] See <https://gcc.gnu.org/bugs/> for instructions.
[mk all 2022-12-20 12:06:41] make[2]: *** [scripts/Makefile.build:250:
kernel/kallsyms.o] Error 1
next prev parent reply other threads:[~2022-12-20 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-84345-4@http.gcc.gnu.org/bugzilla/>
2021-05-14 9:49 ` [Bug rtl-optimization/84345] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:10 ` rguenth at gcc dot gnu.org
2021-09-20 10:43 ` pinskia at gcc dot gnu.org
2021-12-28 10:43 ` pinskia at gcc dot gnu.org
2021-12-28 10:43 ` pinskia at gcc dot gnu.org
2022-05-27 9:38 ` [Bug rtl-optimization/84345] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:34 ` jakub at gcc dot gnu.org
2022-12-20 13:16 ` jbglaw@lug-owl.de [this message]
2022-12-20 16:57 ` pinskia at gcc dot gnu.org
2023-01-19 14:10 ` rguenth at gcc dot gnu.org
2023-07-07 10:33 ` [Bug rtl-optimization/84345] [11/12/13/14 " 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-84345-4-ZYPkkGlEJF@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: link
Be 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).