public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/114929] for loop fails to iterate down to zero if a cardinal type (unsigned type) is used with a step of -1. Date: Fri, 03 May 2024 19:48:41 +0000 [thread overview] Message-ID: <bug-114929-4-p6bgU3UqOl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114929-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114929 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>: https://gcc.gnu.org/g:c943d7b5c40f447b12431df9ad27a47dad95026d commit r15-137-gc943d7b5c40f447b12431df9ad27a47dad95026d Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Fri May 3 20:48:01 2024 +0100 PR modula2/114929 extra for loop iteration count regression tests This patch introduces three more for loop tests checking the iteration count using the CHAR and enumeration data types. gcc/testsuite/ChangeLog: PR modula2/114929 * gm2/pim/run/pass/testforloopchar.mod: New test. * gm2/pim/run/pass/testforloopchar2.mod: New test. * gm2/pim/run/pass/testforloopenum.mod: New test. Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2024-05-03 19:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-02 23:56 [Bug modula2/114929] New: " gaius at gcc dot gnu.org 2024-05-02 23:56 ` [Bug modula2/114929] " gaius at gcc dot gnu.org 2024-05-03 0:01 ` gaius at gcc dot gnu.org 2024-05-03 0:23 ` cvs-commit at gcc dot gnu.org 2024-05-03 0:27 ` gaius at gcc dot gnu.org 2024-05-03 19:48 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-03 21:59 ` cvs-commit at gcc dot gnu.org 2024-05-03 22:29 ` 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-114929-4-p6bgU3UqOl@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).