public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gr.audio at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/109675] New: GCC 13.1: the Modula-2 front-end fails to build on some platforms Date: Sat, 29 Apr 2023 01:19:40 +0000 [thread overview] Message-ID: <bug-109675-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109675 Bug ID: 109675 Summary: GCC 13.1: the Modula-2 front-end fails to build on some platforms Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: gr.audio at gmail dot com Target Milestone: --- Happens on any platform on which the 'long unsigned int' type can't hold a pointer (for instance: Windows/mingw64). The culprit is this: ../../gcc-13.1.0/gcc/m2/mc-boot/GDynamicStrings.cc: In function 'void writeAddress(void*)': ../../gcc-13.1.0/gcc/m2/mc-boot/GDynamicStrings.cc:909:18: error: cast from 'void*' to 'long unsigned int' loses precision [-fpermissive] 909 | writeLongcard ((long unsigned int ) (a)); | ^~~~~~~~~~~~~~~~~~~~~~~~ Casting a pointer to a 'long unsigned int' is not exactly portable.
next reply other threads:[~2023-04-29 1:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-29 1:19 gr.audio at gmail dot com [this message] 2023-05-02 12:34 ` [Bug modula2/109675] " gaius at gcc dot gnu.org 2023-05-03 15:09 ` gaius at gcc dot gnu.org 2023-05-04 0:37 ` cvs-commit at gcc dot gnu.org 2023-05-04 0:42 ` gaius at gcc dot gnu.org 2023-07-28 11:56 ` 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-109675-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).