public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103515] Unexpected OPTION_MASK_SAVE_TOC_INDIRECT of rs6000_isa_flag Date: Wed, 01 Dec 2021 08:29:15 +0000 [thread overview] Message-ID: <bug-103515-4-g18l1yREhN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103515-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103515 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |powerpc --- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> --- Put the below code at the beginning of function rs6000_can_inline_p can make it ICE. tree caller_tree = DECL_FUNCTION_SPECIFIC_TARGET (caller); if (!caller_tree) { caller_tree = target_option_default_node; gcc_assert (rs6000_isa_flags == TREE_TARGET_OPTION (caller_tree)->x_rs6000_isa_flags); } #1 0x0000000011f1ff7c in rs6000_can_inline_p (caller=<function_decl 0x7ffff5c44700 __ct_base >, callee=<function_decl 0x7ffff5c44400 __ct_base >) (gdb) p /x (rs6000_isa_flags ^ TREE_TARGET_OPTION (caller_tree)->x_rs6000_isa_flags) & OPTION_MASK_SAVE_TOC_INDIRECT $2 = 0x10000000000000
next prev parent reply other threads:[~2021-12-01 8:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-01 8:19 [Bug target/103515] New: " linkw at gcc dot gnu.org 2021-12-01 8:29 ` linkw at gcc dot gnu.org [this message] 2021-12-01 9:31 ` [Bug target/103515] " marxin at gcc dot gnu.org 2021-12-02 1:43 ` linkw at gcc dot gnu.org 2021-12-02 1:45 ` linkw at gcc dot gnu.org 2021-12-13 6:22 ` cvs-commit at gcc dot gnu.org 2022-05-19 21:46 ` bergner at gcc dot gnu.org 2022-05-20 2:06 ` linkw 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-103515-4-g18l1yREhN@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).