public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100132] Optimization breaks pointer association
Date: Sun, 18 Apr 2021 09:43:28 +0000	[thread overview]
Message-ID: <bug-100132-4-feo3G7uXzj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100132-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-04-18
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed since at least GCC7.

  parent reply	other threads:[~2021-04-18  9:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 23:38 [Bug fortran/100132] New: " jrfsousa at gmail dot com
2021-04-18  0:20 ` [Bug fortran/100132] " jrfsousa at gmail dot com
2021-04-18  9:43 ` dominiq at lps dot ens.fr [this message]
2022-09-18 19:11 ` anlauf at gcc dot gnu.org
2022-09-19 20:21 ` anlauf at gcc dot gnu.org
2022-09-20 18:31 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:17 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:40 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:55 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:56 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` anlauf 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-100132-4-feo3G7uXzj@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).