public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrfsousa at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c)
Date: Wed, 28 Apr 2021 18:33:43 +0000	[thread overview]
Message-ID: <bug-92621-4-QA5xzUoFyO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92621-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from José Rui Faustino de Sousa <jrfsousa at gmail dot com> ---
(In reply to Dominique d'Humieres from comment #11)
> Did you try to click on 'take' in
> 
> Assignee:	
> Not yet assigned to anyone (edit) (take)
> 

I do not have the "edit" or "take" links and if I click "Not yet assigned to
anyone" it tries to send an email to "unassigned@gcc.gnu.org"...

Thank you very much.

Best regards,
José Rui

  parent reply	other threads:[~2021-04-28 18:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92621-4@http.gcc.gnu.org/bugzilla/>
2020-12-22 13:57 ` briggs.michaels at gmail dot com
2020-12-22 13:58 ` briggs.michaels at gmail dot com
2020-12-22 14:01 ` briggs.michaels at gmail dot com
2020-12-22 14:03 ` briggs.michaels at gmail dot com
2021-04-26 11:23 ` jrfsousa at gmail dot com
2021-04-26 16:54 ` dominiq at lps dot ens.fr
2021-04-28 12:47 ` jrfsousa at gmail dot com
2021-04-28 13:53 ` dominiq at lps dot ens.fr
2021-04-28 18:33 ` jrfsousa at gmail dot com [this message]
2021-04-28 18:49 ` anlauf at gcc dot gnu.org
2021-05-07 10:48 ` jrfsousa at gcc dot gnu.org
2021-05-07 18:23 ` anlauf at gcc dot gnu.org
2021-07-01 21:16 ` sandra at gcc dot gnu.org
2021-07-01 22:21 ` kargl at gcc dot gnu.org
2021-07-02 14:53 ` sandra at gcc dot gnu.org
2021-08-11 14:11 ` burnus at gcc dot gnu.org
2021-10-18  8:29 ` cvs-commit at gcc dot gnu.org
2021-10-21 18:43 ` sandra at gcc dot gnu.org
2021-10-22 11:33 ` burnus at gcc dot gnu.org
2021-10-22 21:49 ` cvs-commit at gcc dot gnu.org
2021-10-22 22:08 ` burnus at gcc dot gnu.org
2022-01-09 23:26 ` pinskia 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-92621-4-QA5xzUoFyO@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).