public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108596] New: error: EDGE_CROSSING missing across section boundary Date: Mon, 30 Jan 2023 11:31:12 +0000 [thread overview] Message-ID: <bug-108596-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108596 Bug ID: 108596 Summary: error: EDGE_CROSSING missing across section boundary Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this C code, derived from yesterday's linux-6.2-rc6: enum { false, true }; __attribute__((__cold__)) _printk(); _static_cpu_has() { asm goto("" : : : : t_yes, t_no); t_yes: return true; t_no: return false; } acpi_sleep_prepare() { _Bool __trans_tmp_1 = _static_cpu_has(); if (!__trans_tmp_1) acpi_set_waking_vector(); _printk(); } does this: $ /home/dcb36/gcc/results/bin/gcc -c -w -std=gnu11 -O2 bug878.c bug878.c: In function ‘acpi_sleep_prepare’: bug878.c:15:1: error: EDGE_CROSSING missing across section boundary 15 | } | ^ during RTL pass: bbpart bug878.c:15:1: internal compiler error: verify_flow_info failed 0x8818f1 verify_flow_info() ../../trunk.d1/gcc/cfghooks.cc:285 $ /home/dcb36/gcc/results/bin/gcc -c -w -std=gnu11 -O1 bug878.c $ The bug first seems to occur sometime before g:9b111debbfb79a0a, dated 20221229.
next reply other threads:[~2023-01-30 11:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 11:31 dcb314 at hotmail dot com [this message] 2023-01-30 12:06 ` [Bug rtl-optimization/108596] " rguenth at gcc dot gnu.org 2023-01-30 12:16 ` [Bug rtl-optimization/108596] [10/11/12/13 Regression] " jakub at gcc dot gnu.org 2023-01-30 12:24 ` jakub at gcc dot gnu.org 2023-01-30 17:08 ` jakub at gcc dot gnu.org 2023-01-31 8:47 ` cvs-commit at gcc dot gnu.org 2023-01-31 8:48 ` [Bug rtl-optimization/108596] [10/11/12 " jakub at gcc dot gnu.org 2023-02-02 9:04 ` dcb314 at hotmail dot com 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-02-10 18:01 ` [Bug rtl-optimization/108596] [10/11 " jakub at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 10:36 ` [Bug rtl-optimization/108596] [10 " jakub at gcc dot gnu.org 2023-05-03 15:20 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:24 ` jakub 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-108596-4@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).