public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/111783] New: 'exit' intrinsic should be marked as
Date: Thu, 12 Oct 2023 11:59:06 +0000 [thread overview]
Message-ID: <bug-111783-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111783
Bug ID: 111783
Summary: 'exit' intrinsic should be marked as
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Target Milestone: ---
Compiling testsuite/gfortran.dg/team_number_1.f90 with -O3 produces the
following optimized dump:
_gfortran_exit_i4 (0);
_gfortran_exit_i4 (0);
_gfortran_stop_numeric (2, 0);
}
The last three statements could be removed as the 'EXIT' intrinsic subroutine
is known not to return.
Thus, we should set
ATTR_NORETURN_NOTHROW_LIST
(cf. fortran/f95-lang.cc).
There are probably more, at least the ABORT intrinsic subroutine and
the functions associated with STOP / ERROR STOP like _gfortran_stop_numeric.
next reply other threads:[~2023-10-12 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:59 burnus at gcc dot gnu.org [this message]
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
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@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).