public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/33387] New: Fortran front-end should translate intrinsics by calling C99 function instead of libgfortran functions Date: Tue, 11 Sep 2007 09:54:00 -0000 [thread overview] Message-ID: <bug-33387-10259@http.gcc.gnu.org/bugzilla/> (raw) Some Fortran intrinsics, like NEAREST or EXPONENT, are translated into calls to libgfortran functions, which in turn call C99 functions. We could easily generate C99 calls directly from the front-end, which would enable further optimization by the middle-end. The list of intrinsics I think of for which we can do that is: EXPONENT, FRACTION, NEAREST, RRSPACING, SET_EXPONENT and SPACING. -- Summary: Fortran front-end should translate intrinsics by calling C99 function instead of libgfortran functions Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: fortran AssignedTo: fxcoudert at gcc dot gnu dot org ReportedBy: fxcoudert at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33387
next reply other threads:[~2007-09-11 9:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-11 9:54 fxcoudert at gcc dot gnu dot org [this message] 2007-09-11 9:55 ` [Bug fortran/33387] " fxcoudert at gcc dot gnu dot org 2007-09-11 9:55 ` fxcoudert at gcc dot gnu dot org 2007-09-11 13:03 ` fxcoudert at gcc dot gnu dot org 2007-09-22 23:35 ` fxcoudert at gcc dot gnu dot org 2007-09-22 23:36 ` fxcoudert at gcc dot gnu dot org 2008-02-25 12:05 ` fxcoudert at gcc dot gnu dot org 2008-02-27 14:33 ` fxcoudert at gcc dot gnu dot org 2008-02-27 14:34 ` 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-33387-10259@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: linkBe 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).