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 ada/98230] incorrect Type'Mod during a loop whose range is computed by a variable
Date: Thu, 10 Dec 2020 21:31:23 +0000	[thread overview]
Message-ID: <bug-98230-4-gLyvXanOWe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98230-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98230

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Eric Botcazou
<ebotcazou@gcc.gnu.org>:

https://gcc.gnu.org/g:bc7d2977d108ed00c30c9f21d5701f28ffb50f29

commit r10-9137-gbc7d2977d108ed00c30c9f21d5701f28ffb50f29
Author: Ed Schonberg <schonberg@adacore.com>
Date:   Thu Dec 10 22:26:57 2020 +0100

    Fix PR ada/98230

    It's a rather curious malfunction of the 'Mod attribute applied to the
    variable of a loop whose upper bound is dynamic.

    gcc/ada/ChangeLog:
            PR ada/98230
            * exp_attr.adb (Expand_N_Attribute_Reference, case Mod): Use base
            type of argument to obtain static bound and required size.

    gcc/testsuite/ChangeLog:
            * gnat.dg/modular6.adb: New test.

  parent reply	other threads:[~2020-12-10 21:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 18:47 [Bug ada/98230] New: Bug in Type'Modulus " adam at vany dot ca
2020-12-10 18:49 ` [Bug ada/98230] " adam at vany dot ca
2020-12-10 20:17 ` ebotcazou at gcc dot gnu.org
2020-12-10 20:18 ` ebotcazou at gcc dot gnu.org
2020-12-10 20:31 ` [Bug ada/98230] incorrect Type'Mod " ebotcazou at gcc dot gnu.org
2020-12-10 21:30 ` cvs-commit at gcc dot gnu.org
2020-12-10 21:31 ` cvs-commit at gcc dot gnu.org [this message]
2020-12-10 21:31 ` cvs-commit at gcc dot gnu.org
2020-12-10 21:32 ` cvs-commit at gcc dot gnu.org
2020-12-10 21:33 ` ebotcazou at gcc dot gnu.org
2020-12-10 21:35 ` adam at vany dot ca

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-98230-4-gLyvXanOWe@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).