This is the mail archive of the gcc-patches@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: [patch] XFAIL anew?.C


Zack Weinberg wrote:

Paul Brook <paul@codesourcery.com> writes:


(But, is using abort() and exit(0) really part of our testsuite
standard?  I thought using return 0/return 1 was perfectly acceptable.
The change is OK, anyhow; that's just a side issue.)

From sourcebuild.texi:


"
Test cases should use @code{abort ()} to indicate failure and
@code{exit (0)} for success; on some targets these may be redefined to
indicate failure and success in other ways.
"


IIRC this is an obsolete constraint having to do with testing on
simulators or embedded boards where the return code from main was not
readily accessible, and has since been dealt with in a general manner
inside dejagnu...?

Poor Paul; he actually read the docs. :-)


OK, since you and Jason agree, a patch to rip out that paragraph is pre-approved by whomever gets there first. :-)

Thanks,

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com


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