https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
--- Comment #6 from Raphael Monod ---
Thank you very much for your explanations. Now I understand why I was wrong. I
will try to change my code to take into account your suggestions.
Once more, thank you very much.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
--- Comment #5 from Janne Blomqvist ---
(In reply to Raphael Monod from comment #4)
> Thank you for your answer. But I don't understand why adding -lpthread
> option change the behavior if I do not use any thread.
In libgfortran, if a thread lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
--- Comment #4 from Raphael Monod ---
Thank you for your answer. But I don't understand why adding -lpthread option
change the behavior if I do not use any thread. Moreover, if I refer to this
page ( https://docs.oracle.com/cd/E19455-01/806-5257/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
Janne Blomqvist changed:
What|Removed |Added
Status|WAITING |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
--- Comment #1 from Richard Biener ---
You may not call arbitrary functions in signal context but only async-signal
safe ones.
