public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tprince@computer.org To: gcc-gnats@gcc.gnu.org Subject: libf2c/7384: DATE_AND_TIME milliseconds field inactive on Windows Date: Mon, 22 Jul 2002 21:16:00 -0000 [thread overview] Message-ID: <20020723041041.17113.qmail@sources.redhat.com> (raw) >Number: 7384 >Category: libf2c >Synopsis: DATE_AND_TIME milliseconds field inactive on Windows >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jul 22 21:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Tim Prince >Release: gcc-3.1.1 >Organization: >Environment: Windows 2K et al >Description: As the current source depends on gettimeofday() to supply the milliseconds field for DATE_AND_TIME(), it is left zero on Windows. Programs which require this information must use a C wrapper to call the Windows API GetLocalTime(). >How-To-Repeat: Execute the u77-test.f program which is included in gcc-testsuite >Fix: Apply the attached patch to libf2c/libU77/datetime_.c, arrange that _WIN32 is pre-defined by gcc for the build of this directory (e.g. by including -mwin32 in CFLAGS when building under cygwin). Note that [de]time_.c also look for _WIN32 to be pre-defined. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="datetime.diff"; name="datetime.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="datetime.diff" KioqIC9ob21lL3RpbS9zcmMvZ2NjLTIwMDIwNDA4L2xpYmYyYy9saWJVNzcvZGF0ZXRpbWVfLmMJ VHVlIEphbiAyMyAxNToyMDozMCAyMDAxCi0tLSBkYXRldGltZV8uYwlTYXQgSnVsIDIwIDEyOjA4 OjA4IDIwMDIKKioqKioqKioqKioqKioqIEJvc3RvbiwgTUEgMDIxMTEtMTMwNywgVVNBLiAgKi8K KioqIDMyLDM1ICoqKioKLS0tIDMyLDQwIC0tLS0KICAjIGVuZGlmCiAgI2VuZGlmCisgI2lmIGRl ZmluZWQgKF9XSU4zMikKKyAjaW5jbHVkZSA8d2luZG93cy5oPgorICN1bmRlZiBtaW4KKyAjdW5k ZWYgbWF4CisgI2VuZGlmCiAgI2luY2x1ZGUgImYyYy5oIgogIAoqKioqKioqKioqKioqKiogaW50 IEc3N19kYXRlX2FuZF90aW1lXzAgKGNoYXIgKmRhdGUsIGNoYQoqKiogNDgsNTEgKioqKgotLS0g NTMsNjQgLS0tLQogICAgY2hhciBkYXRbOV0sIHpvbls2XSwgZnRpbVsxMV07CiAgICBpbnQgaSwg dmFsc1s4XTsKKyAjaWYgZGVmaW5lZCAoX1dJTjMyKQorICAgICBzdHJ1Y3QgX1NZU1RFTVRJTUUg d2RhdHRpbTsKKyAgICAgR2V0TG9jYWxUaW1lKCZ3ZGF0dGltKTsKKyAgICAgdmFsc1s3XSA9IHdk YXR0aW0ud01pbGxpc2Vjb25kczsKKyAjZWxzZQorICAgdmFsc1s3XSA9IDA7ICAgICAgICAgICAg ICAgICAgLyogbm8gU1REQy9QT1NJWCB3YXkgdG8gZ2V0IHRoaXMgKi8KKyAgIC8qIEdOVWlzaCB3 YXk7IG1heWJlIHVzZSBgZnRpbWUnIG9uIG90aGVyIHN5c3RlbXMuICovCisgI2VuZGlmCiAgCiAg ICB2YWxzWzBdID0gMTkwMCArIGx0aW1lLnRtX3llYXI7CioqKioqKioqKioqKioqKiBpbnQgRzc3 X2RhdGVfYW5kX3RpbWVfMCAoY2hhciAqZGF0ZSwgY2hhCioqKiA1OSw2NCAqKioqCiAgICB2YWxz WzVdID0gbHRpbWUudG1fbWluOwogICAgdmFsc1s2XSA9IGx0aW1lLnRtX3NlYzsKLSAgIHZhbHNb N10gPSAwOyAgICAgICAgICAgICAgICAgIC8qIG5vIFNUREMvUE9TSVggd2F5IHRvIGdldCB0aGlz ICovCi0gICAvKiBHTlVpc2ggd2F5OyBtYXliZSB1c2UgYGZ0aW1lJyBvbiBvdGhlciBzeXN0ZW1z LiAqLwogICNpZiBIQVZFX0dFVFRJTUVPRkRBWQogICAgewotLS0gNzIsNzUgLS0tLQo=
next reply other threads:[~2002-07-23 4:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-22 21:16 tprince [this message] 2002-09-14 5:52 toon 2002-09-17 14:29 toon
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=20020723041041.17113.qmail@sources.redhat.com \ --to=tprince@computer.org \ --cc=gcc-gnats@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).