public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/111783] 'exit' intrinsic should be marked as noreturn
Date: Thu, 12 Oct 2023 19:19:17 +0000	[thread overview]
Message-ID: <bug-111783-4-jeOWErBcpe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111783-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111783

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gcc dot gnu.org

--- Comment #2 from anlauf at gcc dot gnu.org ---
(In reply to Tobias Burnus from comment #0)
> There are probably more, at least the ABORT intrinsic subroutine and
> the functions associated with STOP / ERROR STOP like _gfortran_stop_numeric.

trans-decl.cc has:

  /* STOP doesn't return.  */
  TREE_THIS_VOLATILE (gfor_fndecl_stop_numeric) = 1;

  TREE_THIS_VOLATILE (gfor_fndecl_stop_string) = 1;

  TREE_THIS_VOLATILE (gfor_fndecl_error_stop_numeric) = 1;

  TREE_THIS_VOLATILE (gfor_fndecl_error_stop_string) = 1;

plus a few more, so these are already accounted for.  Try:

  stop 1
  error stop 2
  stop "3"
end

The dump-tree-optimized only contains the first even at -O0, as it should be,
shouldn't it?

This leaves ABORT and EXIT to deal with.

  parent reply	other threads:[~2023-10-12 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 11:59 [Bug fortran/111783] New: 'exit' intrinsic should be marked as burnus at gcc dot gnu.org
2023-10-12 16:00 ` [Bug fortran/111783] 'exit' intrinsic should be marked as noreturn pinskia at gcc dot gnu.org
2023-10-12 19:19 ` anlauf at gcc dot gnu.org [this message]
2023-10-12 19:28 ` anlauf 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-111783-4-jeOWErBcpe@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).