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 rtl-optimization/108596] [10/11/12 Regression] error: EDGE_CROSSING missing across section boundary
Date: Thu, 02 Feb 2023 09:04:41 +0000 [thread overview]
Message-ID: <bug-108596-4-GJfFOY3vha@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108596-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108596
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Jakub Jelinek from comment #6)
> Fixed on the trunk so far.
linux-6.2-rc6 builds fine, when built with -O3.
Thanks for the quick fix.
next prev parent reply other threads:[~2023-02-02 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 11:31 [Bug c/108596] New: " dcb314 at hotmail dot com
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 [this message]
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-GJfFOY3vha@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).