public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "José Rui Faustino de Sousa" <jrfsousa@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [Patch, fortran V2] PR fortran/93308/93963/94327/94331/97046 problems raised by descriptor handling
Date: Mon, 21 Jun 2021 17:52:07 +0000	[thread overview]
Message-ID: <a2dc4082-f580-6299-bdfd-e4da4c3274b7@gmail.com> (raw)
In-Reply-To: <cf707115-9386-5f1c-e423-64fbfda5194f@codesourcery.com>

Hi Tobias,

On 21/06/21 16:46, Tobias Burnus wrote:
> Well, as said: directly into the compiler where currently the call to
> libgomp is.
 >

I don't think I understand were you mean. You don't mean the includes in 
"f95-lang.c" do you?

Best regards,
José Rui



  reply	other threads:[~2021-06-21 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 23:09 José Rui Faustino de Sousa
2021-06-21 13:46 ` Tobias Burnus
2021-06-21 15:51   ` José Rui Faustino de Sousa
2021-06-21 16:46     ` Tobias Burnus
2021-06-21 17:52       ` José Rui Faustino de Sousa [this message]
2021-06-21 20:29         ` Tobias Burnus
2021-06-22  7:11           ` Tobias Burnus
2021-07-26 12:43             ` Committed: " Tobias Burnus
  -- strict thread matches above, loose matches on Subject: below --
2021-06-03 15:04 [Patch, fortran] PR fortran/100120/100816/100818/100819/100821 problems raised by aggregate data types dhumieres.dominique
2021-06-04 15:24 ` Paul Richard Thomas
2021-06-05 12:40   ` dhumieres.dominique
2021-06-06 17:58     ` Re:[Patch, fortran] PR fortran/93308/93963/94327/94331/97046 problems raised by descriptor handling dhumieres.dominique
2021-06-19 10:57       ` [Patch, fortran v2] " dhumieres.dominique

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=a2dc4082-f580-6299-bdfd-e4da4c3274b7@gmail.com \
    --to=jrfsousa@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /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).