public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99723] [11/12/13 Regression] arm: ICE in build_function_type during selftests Date: Mon, 10 Oct 2022 13:23:04 +0000 [thread overview] Message-ID: <bug-99723-4-UNTLaT53cu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99723-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99723 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrea Corallo <akrl@gcc.gnu.org>: https://gcc.gnu.org/g:248c8aeebc49aae3fd96bd587367d12e7c8b3c3a commit r13-3201-g248c8aeebc49aae3fd96bd587367d12e7c8b3c3a Author: Andrea Corallo <andrea.corallo@arm.com> Date: Tue Sep 27 16:20:28 2022 +0200 Don't ICE running selftests if errors were raised [PR99723] Hi all this is to address PR 99723. In the PR GCC crashes as the initialization of common trees is not performed as no compilation is happening, this is because we raise an error earlier while processing the arch flags. This patch changes the code to execute selftests only if no errors where raised before. Bootstrapped on aarch64, okay for trunk? Best Regards Andrea 2022-09-27 Andrea Corallo <andrea.corallo@arm.com> PR other/99723 * toplev.cc (toplev::main): Don't run self tests in case of previous error.
next prev parent reply other threads:[~2022-10-10 13:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 10:09 [Bug target/99723] New: " acoplan at gcc dot gnu.org 2021-03-23 10:39 ` [Bug target/99723] " acoplan at gcc dot gnu.org 2021-10-12 16:19 ` [Bug target/99723] [11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-21 13:57 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2022-09-28 12:03 ` [Bug target/99723] [11/12/13 " akrl at gcc dot gnu.org 2022-10-10 13:23 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-29 10:04 ` [Bug target/99723] [11/12/13/14 " 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-99723-4-UNTLaT53cu@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).