public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43837]  New: Set TREE_NOTHROW also on libgfortran library calls
Date: Wed, 21 Apr 2010 17:47:00 -0000	[thread overview]
Message-ID: <bug-43837-13404@http.gcc.gnu.org/bugzilla/> (raw)

Follow up to PR 43836  and  http://gcc.gnu.org/ml/fortran/2010-04/msg00222.html

> It would be good to set TREE_NOTHROW also on libgfortran library calls
> that are known not to throw exceptions (I guess most of them, except
> those that do IO).

POSIX lists which libc functions have to and can throw, cf.
http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html#tag_02_09_05

In the glibc headers one can also look for functions which use __THROW on
prototypes (__THROW means the function never throws) and which don't; also the
__NTH macro and __REDIRECT_NTH.

In libgfortran itself, one can use  __attribute__ ((nothrow)), cf.
http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html

In the front end (call to library routines) TREE_NOTHROW.


-- 
           Summary: Set TREE_NOTHROW also on libgfortran library calls
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43837


             reply	other threads:[~2010-04-21 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 17:47 burnus at gcc dot gnu dot org [this message]
2010-06-11 13:48 ` [Bug fortran/43837] " fxcoudert at gcc dot gnu dot 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-43837-13404@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).