public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/102992] fortran: redirecting standard out to a file does not work on macOS 12.0
Date: Fri, 12 Nov 2021 12:31:37 +0000 [thread overview]
Message-ID: <bug-102992-4-YondBDhR9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102992-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102992
--- Comment #29 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #28)
> > Well, unless there's a good reason to have it in a DTOR, it makes for a more
> > robust solution to call it directly (there are various other differences
> > that could occur in mixed code bases esp. c++ + fortran even without the
> > Darwin21.1 bug).
>
> Mixed code is in fact the reason why it's in a DTOR and not called at the
> end of Fortran main program. We need this clean-up routine to run even when
> the main code is not in Fortran, and but Fortran routines are called by
> other means (Fortran object files linked, or Fortran-based library loaded at
> run-time).
I've posted a fix for this (it is the fix for darwin21 DTORs in general)
however CAVEAT : there is No guarantee given by the GCC DTOR machinery about
the relative ordering of DTORs between different TUs, my fix will not solve
that.
next prev parent reply other threads:[~2021-11-12 12:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 22:34 [Bug fortran/102992] New: Piping in a file does no longer work on macOS Monterey juergen.reuter at desy dot de
2021-10-28 22:37 ` [Bug fortran/102992] " juergen.reuter at desy dot de
2021-10-28 23:11 ` [Bug libfortran/102992] " iains at gcc dot gnu.org
2021-10-28 23:22 ` pinskia at gcc dot gnu.org
2021-10-29 6:41 ` juergen.reuter at desy dot de
2021-10-29 10:04 ` juergen.reuter at desy dot de
2021-10-29 12:40 ` iains at gcc dot gnu.org
2021-10-29 12:51 ` iains at gcc dot gnu.org
2021-10-29 13:12 ` [Bug libfortran/102992] fortran: redirecting standard out to a file does not work on macOS 12.0 iains at gcc dot gnu.org
2021-10-29 14:05 ` juergen.reuter at desy dot de
2021-10-29 15:50 ` juergen.reuter at desy dot de
2021-10-31 0:52 ` townsend at astro dot wisc.edu
2021-11-01 9:09 ` juergen.reuter at desy dot de
2021-11-01 10:51 ` tkoenig at gcc dot gnu.org
2021-11-01 11:10 ` tkoenig at gcc dot gnu.org
2021-11-01 11:17 ` tkoenig at gcc dot gnu.org
2021-11-01 12:22 ` iains at gcc dot gnu.org
2021-11-01 12:25 ` iains at gcc dot gnu.org
2021-11-01 12:49 ` juergen.reuter at desy dot de
2021-11-01 17:37 ` tkoenig at gcc dot gnu.org
2021-11-01 17:41 ` tkoenig at gcc dot gnu.org
2021-11-01 17:44 ` juergen.reuter at desy dot de
2021-11-01 17:50 ` juergen.reuter at desy dot de
2021-11-01 18:08 ` iains at gcc dot gnu.org
2021-11-01 18:53 ` juergen.reuter at desy dot de
2021-11-01 19:00 ` iains at gcc dot gnu.org
2021-11-01 20:47 ` iains at gcc dot gnu.org
2021-11-02 10:39 ` dominiq at lps dot ens.fr
2021-11-12 12:06 ` fxcoudert at gcc dot gnu.org
2021-11-12 12:31 ` iains at gcc dot gnu.org [this message]
2021-11-12 12:40 ` fxcoudert at gcc dot gnu.org
2021-11-15 19:32 ` juergen.reuter at desy dot de
2021-11-15 19:43 ` fxcoudert at gcc dot gnu.org
2021-11-15 19:51 ` cvs-commit at gcc dot gnu.org
2021-11-15 19:55 ` iains at gcc dot gnu.org
2021-12-14 18:39 ` juergen.reuter at desy dot de
2021-12-15 13:06 ` iains at gcc dot gnu.org
2021-12-15 14:06 ` fxcoudert at gcc dot gnu.org
2022-04-14 5:26 ` cvs-commit at gcc dot gnu.org
2022-05-06 8:31 ` jakub at gcc dot gnu.org
2022-05-29 19:15 ` cvs-commit at gcc dot gnu.org
2022-05-29 19:27 ` iains 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-102992-4-YondBDhR9E@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).