Bug 709186 - glibc-2.13.90-14 failed 22_locale/time_get/get_weekday/char/38081-1.cc
Summary: glibc-2.13.90-14 failed 22_locale/time_get/get_weekday/char/38081-1.cc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 01:16 UTC by H.J. Lu
Modified: 2016-11-24 15:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-31 13:39:30 UTC
Type: ---


Attachments (Terms of Use)
A testcase (21.94 KB, application/octet-stream)
2011-05-31 02:12 UTC, H.J. Lu
no flags Details

Description H.J. Lu 2011-05-31 01:16:55 UTC
When I run "make check" in GCC 4.7 under glibc-2.13.90-14 on
ia32 and x86-64, I got

FAIL: 22_locale/time_get/get_weekday/char/38081-1.cc execution test
FAIL: 22_locale/time_get/get_weekday/char/38081-2.cc execution test

Comment 1 H.J. Lu 2011-05-31 02:12:38 UTC
Created attachment 501900 [details]
A testcase

glibc-2.13.90-14:

[hjl@gnu-snb-1 testsuite]$ ./38081-2.exe
38081-2.exe: /export/gnu/import/git/gcc/libstdc++-v3/testsuite/22_locale/time_get/get_weekday/char/38081-2.cc:69: void test01(): Assertion `time01.tm_wday == i' failed.
Aborted (core dumped)
[hjl@gnu-snb-1 testsuite]$ 

glibc-2.13.90-11:

[hjl@gnu-4 testsuite]$ ./38081-2.exe
[hjl@gnu-4 testsuite]$

Comment 2 Andreas Schwab 2011-05-31 13:06:36 UTC
So fix the test.

Comment 3 H.J. Lu 2011-05-31 13:13:00 UTC
Thoses 2 tests have been in GCC for a long time.
Would you mind telling me what is wrong in
those 2 tests? Thanks in advance.

Comment 4 Andreas Schwab 2011-05-31 13:39:30 UTC
f49839299a085505eb673544744b61d2d9cdd1db

Comment 5 H.J. Lu 2011-05-31 13:48:05 UTC
(In reply to comment #4)
> f49839299a085505eb673544744b61d2d9cdd1db

Would you mind telling what it is? Thanks.


Note You need to log in before you can comment on or make changes to this bug.