public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/104065] New: [12 Regression] trunk 20220117 fails to build modula2 Date: Mon, 17 Jan 2022 11:42:57 +0000 [thread overview] Message-ID: <bug-104065-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104065 Bug ID: 104065 Summary: [12 Regression] trunk 20220117 fails to build modula2 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: unassigned at gcc dot gnu.org Reporter: doko at debian dot org Target Milestone: --- seen with trunk 20220117, not seen with 20220116: In file included from ../../src/gcc/system.h:1243, from ../../src/gcc/m2/mc-boot/GArgs.c:29: ../../src/gcc/hwint.h:361:1: error: conflicting types for 'mul_hwi'; have 'long int(long int, long int, unsigned char *)' 361 | mul_hwi (HOST_WIDE_INT a, HOST_WIDE_INT b, bool *overflow) | ^~~~~~~ ../../src/gcc/hwint.h:264:22: note: previous declaration of 'mul_hwi' with type 'long int(long int, long int)' 264 | extern HOST_WIDE_INT mul_hwi (HOST_WIDE_INT, HOST_WIDE_INT); | ^~~~~~~
next reply other threads:[~2022-01-17 11:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 11:42 doko at debian dot org [this message] 2022-01-18 4:34 ` [Bug modula2/104065] " pinskia at gcc dot gnu.org 2022-01-18 7:26 ` rguenth at gcc dot gnu.org 2022-01-18 11:21 ` gaius at gcc dot gnu.org 2022-01-18 14:19 ` gaius at gcc dot gnu.org 2022-01-18 14:33 ` gaius at gcc dot gnu.org 2022-01-19 10:50 ` doko at debian dot org 2022-01-20 16:14 ` gaius at gcc dot gnu.org 2022-01-21 14:40 ` gaius at gcc dot gnu.org 2022-01-22 0:58 ` gaius at gcc dot gnu.org 2022-03-09 13:29 ` rguenth 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-104065-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).