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/109713] [14 Regression] gcc/config/riscv/sync.md:66:1: error: control reaches end of non-void function [-Werror=return-type] since r14-406-gbff7c773864479 Date: Mon, 31 Jul 2023 16:19:29 +0000 [thread overview] Message-ID: <bug-109713-4-LT8LLsVfk8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109713-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109713 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Patrick O'Neill <poneill@gcc.gnu.org>: https://gcc.gnu.org/g:1e9180b3298def6c01d9055d558fdb52231f8d2d commit r13-7674-g1e9180b3298def6c01d9055d558fdb52231f8d2d Author: Martin Liska <mliska@suse.cz> Date: Wed May 3 16:35:26 2023 +0200 riscv: fix error: control reaches end of non-void function Fixes: gcc/config/riscv/sync.md:66:1: error: control reaches end of non-void function [-Werror=return-type] 66 | [(set (attr "length") (const_int 4))]) | ^ PR target/109713 gcc/ChangeLog: * config/riscv/sync.md: Add gcc_unreachable to a switch.
prev parent reply other threads:[~2023-07-31 16:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 12:16 [Bug target/109713] New: " marxin at gcc dot gnu.org 2023-05-03 12:17 ` [Bug target/109713] " marxin at gcc dot gnu.org 2023-05-03 12:20 ` marxin at gcc dot gnu.org 2023-05-03 12:22 ` marxin at gcc dot gnu.org 2023-05-03 12:25 ` jakub at gcc dot gnu.org 2023-05-03 12:32 ` marxin at gcc dot gnu.org 2023-05-03 12:33 ` jakub at gcc dot gnu.org 2023-05-03 13:10 ` rguenth at gcc dot gnu.org 2023-05-03 14:37 ` cvs-commit at gcc dot gnu.org 2023-05-03 14:37 ` marxin at gcc dot gnu.org 2023-07-31 16:19 ` cvs-commit at gcc dot gnu.org [this message]
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-109713-4-LT8LLsVfk8@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).