Opened 13 years ago
Closed 13 years ago
#2938 closed defect (fixed)
GCC test failures with Glibc-2.14
| Reported by: | Matthew Burgess | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.0 |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Hi,
On my most recent build, I noticed that 2 of the locale tests in the libstdc++ test suite failed. There's a patch at http://gcc.gnu.org/viewcvs?view=revision&revision=176643 which should fix it. The bug is at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49293
Change History (4)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
I see a timeout related failure in stdio-common/bug22.out as well as the same failure in posix/bug-regex32.out that you do. Other than that, all of mine pass.
comment:3 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Added a patch to gcc to correct for locale issues. Added an additional comment about glibc test failures.
Fixed at revision 9626.
Note:
See TracTickets
for help on using tickets.
I don't see those errors. This is the complete set of errors for me:
The regex is a test suite error: http://old.nabble.com/-Bug-libc-13118--New%3A-Correct-posix-bug-regex32-testsuite-failure-td32298542.html
Arch Linux has the tst-writev error as a x86_54 only error. There are indications that it is a timing error. I didn't try adjusting the TIMEOUTFACTOR.
Roland McGrath thinks the check-textrel is a binutils bug.
I'm not sure we should be chasing down every failure we see in glibc. Many are architecture or timing specific. I'd rather just document the test failures we see.