public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/22359] fseek intrinsic not implemented Date: Fri, 04 May 2007 18:35:00 -0000 [thread overview] Message-ID: <20070504183520.2991.qmail@sourceware.org> (raw) In-Reply-To: <bug-22359-10581@http.gcc.gnu.org/bugzilla/> -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.1/4.2 regression] fseek |fseek intrinsic not |intrinsic not implemented |implemented Target Milestone|4.3.0 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22359
next prev parent reply other threads:[~2007-05-04 18:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-22359-10581@http.gcc.gnu.org/bugzilla/> 2007-04-29 23:19 ` [Bug fortran/22359] fseek intrinsic appears to be unimplemented dfranke at gcc dot gnu dot org 2007-05-01 9:56 ` dfranke at gcc dot gnu dot org 2007-05-04 18:34 ` [Bug fortran/22359] [4.1/4.2 regression] fseek intrinsic not implemented dfranke at gcc dot gnu dot org 2007-05-04 18:35 ` pinskia at gcc dot gnu dot org [this message] 2007-05-27 8:49 ` [Bug fortran/22359] " tkoenig at gcc dot gnu dot org 2007-06-16 22:51 ` dfranke 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=20070504183520.2991.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).