public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jblomqvi at cc dot hut dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20786] Can't use AINT intrinsic with KIND parameter Date: Sat, 11 Jun 2005 20:07:00 -0000 [thread overview] Message-ID: <20050611200743.23499.qmail@sourceware.org> (raw) In-Reply-To: <20050406095442.20786.fxcoudert@gcc.gnu.org> ------- Additional Comments From jblomqvi at cc dot hut dot fi 2005-06-11 20:07 ------- Actually, ANINT also exhibits the same problem: implicit none real(4) :: r = 42.7, r2 r2 = aint (r,kind=8) print *, 'aint: ', r2 r2 = anint (r, kind=8) print *, 'anint: ', r2 end Prints out: aint: 0.000000 anint: 0.000000 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20786
next prev parent reply other threads:[~2005-06-11 20:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-06 9:54 [Bug fortran/20786] New: " fxcoudert at gcc dot gnu dot org 2005-04-06 15:12 ` [Bug fortran/20786] " pinskia at gcc dot gnu dot org 2005-05-23 18:25 ` jblomqvi at cc dot hut dot fi 2005-06-11 20:07 ` jblomqvi at cc dot hut dot fi [this message] [not found] <bug-20786-10259@http.gcc.gnu.org/bugzilla/> 2005-10-11 23:58 ` cvs-commit at gcc dot gnu dot org 2005-10-12 0:31 ` cvs-commit at gcc dot gnu dot org 2005-10-12 0:33 ` kargl 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=20050611200743.23499.qmail@sourceware.org \ --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).