From: Joseph Myers <joseph@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>, <fortran@gcc.gnu.org>
Subject: Re: [ping] driver: Forward '-lgfortran', '-lm' to offloading compilation
Date: Tue, 13 Jun 2023 15:34:41 +0000 [thread overview]
Message-ID: <6bdae2bd-a3b2-6b9-397b-b129314f17@codesourcery.com> (raw)
In-Reply-To: <87r0qf7ibj.fsf@euler.schwinge.homeip.net>
On Tue, 13 Jun 2023, Thomas Schwinge wrote:
> Hi!
>
> On 2023-06-05T14:25:18+0200, I wrote:
> > OK to push the attached
> > "driver: Forward '-lgfortran', '-lm' to offloading compilation"?
> > (We didn't have a PR open for that, or did we?)
>
> Ping.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-06-13 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 12:25 Thomas Schwinge
2023-06-13 10:44 ` [ping] " Thomas Schwinge
2023-06-13 15:34 ` Joseph Myers [this message]
2023-06-14 10:13 ` Tobias Burnus
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=6bdae2bd-a3b2-6b9-397b-b129314f17@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=thomas@codesourcery.com \
--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).