public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109713] New: [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: Wed, 03 May 2023 12:16:25 +0000 [thread overview] Message-ID: <bug-109713-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109713 Bug ID: 109713 Summary: [14 Regression] gcc/config/riscv/sync.md:66:1: error: control reaches end of non-void function [-Werror=return-type] since r14-406-gbff7c773864479 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: patrick at rivosinc dot com Target Milestone: --- Host: x86_64-linux-gnu Target: riscv64-unknown-linux-gnu Since the revision I see: [ 5046s] ../../gcc/config/riscv/sync.md: In function 'const char* output_479(rtx_def**, rtx_insn*)': [ 5046s] ../../gcc/config/riscv/sync.md:66:1: error: control reaches end of non-void function [-Werror=return-type] [ 5046s] 66 | [(set (attr "length") (const_int 4))]) [ 5046s] | ^ [ 5046s] cc1plus: some warnings being treated as errors
next reply other threads:[~2023-05-03 12:16 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 12:16 marxin at gcc dot gnu.org [this message] 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
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@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).