public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49627] NINT(x,16) doesn't work (at all, ever, I don't think) Date: Sun, 24 Jul 2011 20:04:00 -0000 [thread overview] Message-ID: <bug-49627-4-Z9BHs5lnvR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49627-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49627 Daniel Franke <dfranke at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfranke at gcc dot gnu.org Severity|blocker |normal --- Comment #2 from Daniel Franke <dfranke at gcc dot gnu.org> 2011-07-24 20:03:56 UTC --- Fortran bugs are never blockers.
next prev parent reply other threads:[~2011-07-24 20:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-04 11:57 [Bug fortran/49627] New: " marcus.appleby at gmail dot com 2011-07-04 12:12 ` [Bug fortran/49627] " burnus at gcc dot gnu.org 2011-07-24 20:04 ` dfranke at gcc dot gnu.org [this message] 2013-01-07 23:02 ` dominiq at lps dot ens.fr
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-49627-4-Z9BHs5lnvR@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).