public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111425] ia64: ICE in net/ipv4/fib_semantics.c:1621:1: internal compiler error: Segmentation fault Date: Fri, 15 Sep 2023 12:10:16 +0000 [thread overview] Message-ID: <bug-111425-4-yRLESwFim8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111425-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111425 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Target| |ia64 Last reconfirmed| |2023-09-15 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed on trunk - we ICE in cselib during var-tracking, so -fno-var-tracking would be a workaround (or -g0). We ICE processing mo->insn (call_insn:TI 6446 8040 8038 59 (parallel [ (set (reg:DI 8 r8) (call (mem:DI (symbol_ref:DI ("memset") [flags 0x41] <function_decl 0x7ffff6f2d200 __builtin_memset>) [0 S8 A64]) (const_int 0 [0]))) (clobber (reg:DI 320 b0)) ]) "net/ipv4/fib_semantics.c":703:3 330 {call_value_nogp} (expr_list:REG_DEAD (reg:DI 122 r74) (expr_list:REG_DEAD (reg:SI 121 r73) (expr_list:REG_DEAD (reg:DI 120 r72) (expr_list:REG_DEAD (reg:DI 1 r1) (expr_list:REG_UNUSED (reg:DI 8 r8) (expr_list:REG_CALL_DECL (symbol_ref:DI ("memset") [flags 0x41] <function_decl 0x7ffff6f2d200 __builtin_memset>) (nil))))))) (expr_list (use (reg:DI 1 r1)) (expr_list:DI (set (reg:DI 8 r8) (reg:DI 120 r72)) (expr_list:DI (use (reg:DI 120 r72)) (expr_list:SI (use (reg:SI 121 r73)) (expr_list:DI (use (reg:DI 122 r74)) (nil)))))))
next prev parent reply other threads:[~2023-09-15 12:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-15 11:36 [Bug target/111425] New: " frank.scheiner at web dot de 2023-09-15 11:40 ` [Bug target/111425] " frank.scheiner at web dot de 2023-09-15 12:10 ` rguenth at gcc dot gnu.org [this message] 2023-09-15 13:11 ` rguenth at gcc dot gnu.org 2023-09-16 8:47 ` frank.scheiner at web dot de 2023-09-18 9:11 ` frank.scheiner at web dot de 2023-09-21 11:10 ` frank.scheiner at web dot de 2023-10-08 11:50 ` frank.scheiner at web dot de 2023-10-09 16:22 ` tglozar at gmail dot com
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-111425-4-yRLESwFim8@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).