This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, libgfortran] Remove recursion check
- From: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- To: Thomas Koenig <tkoenig at netcologne dot de>
- Cc: jerry DeLisle <jvdelisle at charter dot net>, Fortran List <fortran at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 8 Nov 2018 21:48:12 +0200
- Subject: Re: [PATCH, libgfortran] Remove recursion check
- References: <20180924085658.26505-1-blomqvist.janne@gmail.com> <1563ef8d-8aef-ac3b-cee5-58428db71f35@netcologne.de> <CAO9iq9FBxQ+OB_N4wU8i=uhKKQVp1XmO0tYyV1zdZmL2gEO9kg@mail.gmail.com> <CAO9iq9FcfvPiW+jqkh6wEk+bkJmvn5ypPKft3jaGhD61A8W_Jg@mail.gmail.com> <978e3b38-cc02-65c1-a0b6-2a9bf77a8f9b@charter.net> <5866f880-e636-1cc4-646c-7a7ef02fee13@netcologne.de> <CAO9iq9E91LMV9K3uco346e0s=pTxi0gZT1abecogHUzwTWTkiA@mail.gmail.com> <a0cf52b0-bf21-75b5-8c19-18fc8e6b7f8f@netcologne.de>
On Sun, Oct 7, 2018 at 12:36 AM Thomas Koenig <tkoenig@netcologne.de> wrote:
> Hi Janne,
>
> > The error handling functions can be called from a signal handler, so they
> > need to be async-signal-safe.
>
> I didn't know that. How can this happen?
>
Hmm, seems I was imagining things, I can't find anything like that in the
code.
Anyway, the more I think about it the better I like my original patch
1) It's KISS
2) I can't find anything in the code that would lead to endless recursive
invocation of the error printing functions.
So, Ok for trunk?
--
Janne Blomqvist