--- Comment #27 from phil at nwl dot cc 2010-01-16 01:08 ---
(In reply to comment #26)
> Hey, I'm telling you the way we all library maintainers (like me) and users
> check the library: they all fetch everything (either mainline or 4_4-branch,
> or
> whatever) via svn,
--- Comment #25 from phil at nwl dot cc 2010-01-15 23:49 ---
(In reply to comment #24)
> (In reply to comment #23)
> > What we want to do is to run the libstdc++ testsuite with my
> > distribution-provided g++, in order to see whether it's generally broken or
> &
--- Comment #23 from phil at nwl dot cc 2010-01-15 22:32 ---
(In reply to comment #22)
> (In reply to comment #21)
> > (In reply to comment #18)
> > > Just build everything with default configure options, then go inside the
> > > libstdc++-v3 *buil
--- Comment #21 from phil at nwl dot cc 2010-01-15 22:07 ---
(In reply to comment #18)
> Just build everything with default configure options, then go inside the
> libstdc++-v3 *build* dir and type 'make check'.
Ah, hmm. Well, having to compile everything in order
--- Comment #17 from phil at nwl dot cc 2010-01-15 01:55 ---
(In reply to comment #16)
> (output files g++.{log,sum} follow as attachments)
Mkay, bugzilla doesn't like the big logs. Meanwhile, take these:
- http://nwl.cc/~n0-1/g++.log
- http://nwl.cc/~n0-1/g++.sum
--
--- Comment #16 from phil at nwl dot cc 2010-01-15 01:49 ---
(In reply to comment #14)
> I'll give the testsuite a try, but this will take some time (svn checkout is
> still running).
>
Oh boy, here it comes. I hope I've done the right thing, as there is little
docu
--- Comment #14 from phil at nwl dot cc 2010-01-14 01:13 ---
(In reply to comment #12)
> Before anything else, you should make sure your system is otherwise sane, I
> don't know "Linux nuty" and I have no idea if it's affected by specific
> issues.
--- Comment #11 from phil at nwl dot cc 2010-01-13 22:52 ---
(In reply to comment #9)
> But note that I can't reproduce it on x86_64 and -m32
>
Was told that, too. So what can I do to support you? What additional
information should I provide? I could probably setup some s
--- Comment #8 from phil at nwl dot cc 2010-01-13 22:37 ---
(In reply to comment #4)
> I cannot reproduce the problem in current 4_4-branch and mainline. Jon does it
> make any sense to you?
>
It seems like this bug exists only on x86 machines, but I don't have any
--- Comment #7 from phil at nwl dot cc 2010-01-13 22:34 ---
(In reply to comment #6)
> does the g++ binary, gcc (GCC) 4.4.2 20091208 (prerelease), match the shared
> library, /usr/lib/libstdc++.so.6.0.13?
>
Yes, it does. The executable is linked against libstdc++.so.6, being
--- Comment #3 from phil at nwl dot cc 2010-01-13 20:23 ---
Created an attachment (id=19582)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19582&action=view)
output when running the test program through valgrind
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734
--- Comment #2 from phil at nwl dot cc 2010-01-13 20:23 ---
Created an attachment (id=19581)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19581&action=view)
assembly output generated by -save-temps
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734
--- Comment #1 from phil at nwl dot cc 2010-01-13 20:22 ---
Created an attachment (id=19580)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19580&action=view)
preprocessor output generated by -save-temps
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734
Product: gcc
Version: 4.4.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: phil at nwl dot cc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734
14 matches
Mail list logo
