public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rbmj at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53456] Add time support for VxWorks Date: Wed, 23 May 2012 13:13:00 -0000 [thread overview] Message-ID: <bug-53456-4-5N3YUfZPjj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53456-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53456 --- Comment #4 from rbmj at verizon dot net 2012-05-23 13:10:14 UTC --- VxWorks does not provide the process time in most versions and for most cases. In fact, many VxWorks applications are not processes in the traditional sense but instead tasks/threads spawned by the kernel in kernel space. If returning an error is the preferred behavior for gf_cputime, then the code as is should work. But it doesn't seem optimal (IMHO) to only have second resolution for gf_gettime. If that is OK though, and preferable to introducing new code (I could understand why), then that is fine too. Also, I started working on this before realizing that the reason it failed to compile initially was mis-configuration. It should compile as-is, just not work as well as (I believe) it could.
next prev parent reply other threads:[~2012-05-23 13:10 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-22 19:04 [Bug fortran/53456] New: " rbmj at verizon dot net 2012-05-22 19:06 ` [Bug fortran/53456] " rbmj at verizon dot net 2012-05-23 8:04 ` jb at gcc dot gnu.org 2012-05-23 9:47 ` burnus at gcc dot gnu.org 2012-05-23 13:13 ` rbmj at verizon dot net [this message] 2012-05-23 14:58 ` jb at gcc dot gnu.org 2012-05-23 15:37 ` burnus at gcc dot gnu.org 2012-05-23 19:09 ` jb at gcc dot gnu.org 2012-05-24 14:01 ` rbmj at verizon dot net 2012-05-24 20:22 ` jb at gcc dot gnu.org 2012-06-04 19:14 ` jb at gcc dot gnu.org 2012-06-04 19:15 ` jb at gcc dot gnu.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-53456-4-5N3YUfZPjj@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).