public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/108551] gcc/m2/gm2-libs-pim/Termbase.mod:128:1: error: control reaches end of non-void function [-Werror=return-type]
Date: Thu, 26 Jan 2023 18:45:29 +0000 [thread overview]
Message-ID: <bug-108551-4-eVEt5imsQZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108551-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
Gaius Mulley <gaius at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #54354|0 |1
is obsolete| |
--- Comment #7 from Gaius Mulley <gaius at gcc dot gnu.org> ---
Created attachment 54357
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54357&action=edit
Proposed fix
This patch follows on from the previous patch to implement the handling of <*
noreturn *> attribute in cc1gm2. I've added Termbase.mod to the testsuite gm2
warnings pass. It builds and causes no further regressions (without
bootstrap).
Once I've seen it build full bootstrap I'll git push the changes.
next prev parent reply other threads:[~2023-01-26 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 7:33 [Bug modula2/108551] New: " rguenth at gcc dot gnu.org
2023-01-26 7:35 ` [Bug modula2/108551] " rguenth at gcc dot gnu.org
2023-01-26 8:33 ` rguenth at gcc dot gnu.org
2023-01-26 9:27 ` marxin at gcc dot gnu.org
2023-01-26 10:28 ` marxin at gcc dot gnu.org
2023-01-26 12:54 ` rguenth at gcc dot gnu.org
2023-01-26 16:24 ` gaius at gcc dot gnu.org
2023-01-26 16:41 ` gaius at gcc dot gnu.org
2023-01-26 18:45 ` gaius at gcc dot gnu.org [this message]
2023-01-26 21:44 ` gaius at gcc dot gnu.org
2023-01-27 7:43 ` rguenth at gcc dot gnu.org
2023-01-27 9:38 ` marxin at gcc dot gnu.org
2023-02-01 17:26 ` cvs-commit at gcc dot gnu.org
2023-02-03 9:01 ` gaius at gcc dot gnu.org
2023-02-03 9:17 ` marxin 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-108551-4-eVEt5imsQZ@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).