--- Comment #14 from jvdelisle at gcc dot gnu dot org 2008-05-07 02:29
---
Subject: Bug 34974
Author: jvdelisle
Date: Wed May 7 02:28:45 2008
New Revision: 135017
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=135017
Log:
2008-05-06 Jerry DeLisle [EMAIL PROTECTED]
PR
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-05-07 02:32
---
I committed the XFAILed test case. Sorry for the inconvenience.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36156
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-05-07 02:33
---
Closing
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from mrs at apple dot com 2008-05-07 02:40 ---
Adding:
+_ZN9__gnu_cxx18stdio_sync_filebufIcSt11char_traitsIcEE4syncEv;
+_ZN9__gnu_cxx18stdio_sync_filebufIcSt11char_traitsIcEE5uflowEv;
+_ZN9__gnu_cxx18stdio_sync_filebufIcSt11char_traitsIcEE6xsgetnEPci;
+
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2008-05-07 02:45
---
One of the problems here is how to do a test case for writing to stdout. We
would have to create a pipe and write to it and read back from the other side.
I don't know how to do that in the testsuite.
--
--- Comment #4 from mrs at apple dot com 2008-05-07 02:58 ---
Thinking and supposing are bad substitutes for solid engineering.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36164
--- Comment #8 from bangerth at dealii dot org 2008-05-07 04:17 ---
The point is: without the complete source code nothing definitive can
be said whether it's the compiler's or the programmer's fault. Your chances
that someone will take the time to try to understand what's going on
--- Comment #3 from bangerth at dealii dot org 2008-05-07 04:21 ---
How is the compiler supposed to know about what alignment malloc can
produce? How can it know that ::operator new doesn't increase the
alignment automatically?
W.
--
bangerth at dealii dot org changed:
--- Comment #7 from ian at airs dot com 2008-05-07 04:39 ---
I'll approve the patch. I think it's correct. I'll check it in in a day or
two, or you can go ahead and do it if you are ready. Thanks for testing it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36013
Since both C++ and Objective-C support foreign exceptions, they should be
tested. I don't know where the best place to put the testcase. I want to say
the Objective-C testsuite and add a check to make sure the C++ front-end was
built.
--
Summary: Foreign exceptions for Objective-C
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-05-07 04:52 ---
Mine.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from hjl dot tools at gmail dot com 2008-05-07 04:56 ---
The default new operator is implemented within gcc. It should be
possible to let g++ know the alignment returned by the new operator.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-05-07 05:00 ---
(In reply to comment #4)
The default new operator is implemented within gcc. It should be
possible to let g++ know the alignment returned by the new operator.
The default one is but the user can override it as
101 - 113 of 113 matches
Mail list logo
