From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Michael Schneider via Fortran <fortran@gcc.gnu.org>
Subject: Re: program errors with GNU Fortran
Date: Fri, 16 Jun 2023 14:49:29 -0700 [thread overview]
Message-ID: <ZIzY6aVAcugXA/8R@troutmask.apl.washington.edu> (raw)
In-Reply-To: <SJ0PR06MB8593DEACBD15F87C2674FAFCFE58A@SJ0PR06MB8593.namprd06.prod.outlook.com>
On Fri, Jun 16, 2023 at 07:18:54PM +0000, Michael Schneider via Fortran wrote:
> Hello,
>
> I'm looking for a forum that can provide answers to
> questions arising with GNU Fortran. Is this the right place?
>
fortran@gcc is normally used for discussion about the
development of the gfortran compiler. However, if a
users has hit a bug within gfortran (a so-called
internal compiler error), one is encouraged to report
it either here or in bugzilla. If your questions are
somewhat generic Fortran question, and you just happen
to use gfortran as your compiler, then those questions
should be addressed to the comp.lang.fortran USENET
newsgroup or stackoverflow.
--
Steve
next prev parent reply other threads:[~2023-06-16 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 19:18 Michael Schneider
2023-06-16 21:49 ` Steve Kargl [this message]
2023-06-17 23:19 ` Jerry D
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=ZIzY6aVAcugXA/8R@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@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).