public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113467] [14 regression] libgcrypt-1.10.3 is miscompiled Date: Thu, 18 Jan 2024 09:32:33 +0000 [thread overview] Message-ID: <bug-113467-4-FZvpG7MK7E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113467-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113467 --- Comment #9 from Sam James <sjames at gcc dot gnu.org> --- I get an ICE with that: ``` /tmp/build/./gcc/xgcc -B/tmp/build/./gcc/ -B/tmp/gcc/x86_64-pc-linux-gnu/bin/ -B/tmp/gcc/x86_64-pc-linux-gnu/lib/ -isystem /tmp/gcc/x86_64-pc-linux-gnu/include -isystem /tmp/gcc/x86_64-pc-linux-gnu/sys-include -g -O2 -m32 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -mlong-double-80 -DUSE_ELF_SYMVER -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fpic -mlong-double-80 -DUSE_ELF_SYMVER -I. -I. -I../../.././gcc -I/home/sam/git/gcc/libgcc -I/home/sam/git/gcc/libgcc/. -I/home/sam/git/gcc/libgcc/../gcc -I/home/sam/git/gcc/libgcc/../include -I/home/sam/git/gcc/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o bid128_div.o -MT bid128_div.o -MD -MP -MF bid128_div.dep -c /home/sam/git/gcc/libgcc/config/libbid/bid128_div.c during GIMPLE pass: vect In file included from /home/sam/git/gcc/libgcc/config/libbid/bid_internal.h:27, from /home/sam/git/gcc/libgcc/config/libbid/bid_div_macros.h:27, from /home/sam/git/gcc/libgcc/config/libbid/bid128_div.c:25: /home/sam/git/gcc/libgcc/config/libbid/bid128_div.c: In function '__bid128_div': /home/sam/git/gcc/libgcc/config/libbid/bid_conf.h:181:20: internal compiler error: in single_pred_edge, at basic-block.h:342 181 | #define bid128_div __bid128_div | ^~~~~~~~~~~~ /home/sam/git/gcc/libgcc/config/libbid/bid_conf.h:1047:6: note: in definition of macro 'BID128_FUNCTION_ARG2' 1047 | fn_name (UINT128 bid_##arg_name1, \ | ^~~~~~~ /home/sam/git/gcc/libgcc/config/libbid/bid128_div.c:36:23: note: in expansion of macro 'bid128_div' 36 | BID128_FUNCTION_ARG2 (bid128_div, x, y) | ^~~~~~~~~~ Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. make[4]: *** [Makefile:653: bid128_div.o] Error 1 ``` Reduced: ``` typedef struct { int w; } UINT128; UINT128 get_BID128_coeff; int get_BID128_coeff_0_1, get_BID128_coeff_0_0, get_BID128_tmp2, get_BID128_expon; void get_BID128() { while ((get_BID128_coeff.w || get_BID128_coeff_0_0) && get_BID128_expon) { if (get_BID128_tmp2) get_BID128_coeff_0_1++; get_BID128_expon--; } } ```
next prev parent reply other threads:[~2024-01-18 9:32 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 5:21 [Bug tree-optimization/113467] New: " sjames at gcc dot gnu.org 2024-01-18 5:22 ` [Bug tree-optimization/113467] " sjames at gcc dot gnu.org 2024-01-18 5:23 ` sjames at gcc dot gnu.org 2024-01-18 5:23 ` sjames at gcc dot gnu.org 2024-01-18 5:24 ` sjames at gcc dot gnu.org 2024-01-18 5:46 ` sjames at gcc dot gnu.org 2024-01-18 6:53 ` sjames at gcc dot gnu.org 2024-01-18 8:22 ` rguenth at gcc dot gnu.org 2024-01-18 8:49 ` rguenth at gcc dot gnu.org 2024-01-18 8:51 ` rguenth at gcc dot gnu.org 2024-01-18 9:32 ` sjames at gcc dot gnu.org [this message] 2024-01-18 9:35 ` sjames at gcc dot gnu.org 2024-01-18 13:16 ` rguenth at gcc dot gnu.org 2024-01-18 16:47 ` sjames at gcc dot gnu.org 2024-01-19 2:31 ` sjames at gcc dot gnu.org 2024-01-19 3:00 ` sjames at gcc dot gnu.org 2024-01-19 7:06 ` rguenth at gcc dot gnu.org 2024-01-19 11:36 ` jakub at gcc dot gnu.org 2024-01-19 13:37 ` rguenth at gcc dot gnu.org 2024-01-23 16:11 ` sjames at gcc dot gnu.org 2024-01-23 17:06 ` tnfchris at gcc dot gnu.org 2024-01-23 17:42 ` rguenther at suse dot de 2024-01-23 17:47 ` tnfchris at gcc dot gnu.org 2024-01-24 7:32 ` rguenth at gcc dot gnu.org 2024-01-26 13:28 ` rguenth at gcc dot gnu.org 2024-01-26 13:33 ` sjames at gcc dot gnu.org 2024-01-26 13:44 ` sjames at gcc dot gnu.org 2024-01-26 14:04 ` tnfchris at gcc dot gnu.org 2024-01-26 19:45 ` kacper.slominski72 at gmail dot com 2024-01-29 18:09 ` tnfchris at gcc dot gnu.org 2024-01-30 8:01 ` sjames at gcc dot gnu.org 2024-02-01 21:56 ` sjames at gcc dot gnu.org 2024-02-02 23:56 ` cvs-commit at gcc dot gnu.org 2024-02-03 22:03 ` sjames at gcc dot gnu.org 2024-02-07 10:57 ` cvs-commit 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-113467-4-FZvpG7MK7E@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).