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/108121] Failing tests on x86_64-linux-gnu Date: Wed, 26 Apr 2023 00:28:41 +0000 [thread overview] Message-ID: <bug-108121-4-roulXTQyA9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108121-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108121 --- Comment #6 from Gaius Mulley <gaius at gcc dot gnu.org> --- Created attachment 54920 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54920&action=edit Proposed fix for TestLong4.mod (ZTYPE fix) Here is a proposed patch to allow testLong4.mod to compile without warning. The ZTYPE is changed to int128 (or int64) if int128 is unavailable and constant literals are built from widest_int. The widest_int is converted into the tree type and checked for overflow. m2expr_interpret_integer and append_m2_digit are removed.
next prev parent reply other threads:[~2023-04-26 0:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-15 9:13 [Bug modula2/108121] New: " marxin at gcc dot gnu.org 2022-12-15 9:14 ` [Bug modula2/108121] " marxin at gcc dot gnu.org 2022-12-15 9:14 ` marxin at gcc dot gnu.org 2022-12-15 9:23 ` marxin at gcc dot gnu.org 2022-12-20 14:26 ` jakub at gcc dot gnu.org 2023-01-15 13:22 ` gaius at gcc dot gnu.org 2023-01-15 13:28 ` gaius at gcc dot gnu.org 2023-04-26 0:28 ` gaius at gcc dot gnu.org [this message] 2023-04-26 1:24 ` gaius at gcc dot gnu.org 2023-04-26 1:57 ` cvs-commit at gcc dot gnu.org 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-07-27 9:24 ` rguenth at gcc dot gnu.org 2023-07-28 2:10 ` cvs-commit at gcc dot gnu.org 2023-07-28 2:28 ` gaius 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-108121-4-roulXTQyA9@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).