This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libstdc++ XPASS's on Darwin


Mike,
   Well, I note sure how to handle some of these testcases. For instance,
1_strings/basic_string/element_access/char/21674.cc has...

// { dg-require-debug-mode "" }
// { dg-options "-O0 -D_GLIBCXX_DEBUG" }
// { dg-do run { xfail *-*-* } }

...which I assume implies that it really should only be set to fail
on systems which use glibc. Does the xfail statement have some 
boolean logic available so that we can say xfail on all systems
that aren't darwin8? 21_strings/basic_string/element_access/wchar_t/21674.cc
appears to be the same situation.
   The 23_containers/vector/resize/1.cc is  Radar 3884894 and can
be fixed by just deleting "// { dg-do run { xfail *-*-darwin8* } }".
The 26_numerics/cmath/c99_classification_macros_c.cc xfail can
be fixed by just deleting the "*-*-darwin*" sections. Lastly,
27_io/ios_base/storage/2.cc is Radar 3884894 (same as 1.cc) and
explicitly notes that Darwin 8 fails because malloc doesn't return
a NULL even if an allocation fails. I assume that may have been fixed
by MacOS X 10.4.7. Could you check that Radar number? I don't know
if I have access to it through my generic connect.apple.com account.
               Jack


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]