e12605764d
gcc/ 2007-07-02 Sandra Loosemore <sandra@codesourcery.com> Richard Sandiford <richard@codesourcery.com> Nigel Stephens <nigel@mips.com> * config/mips/mips-protos.h (mips16e_save_restore_info): New struct. (mips16e_output_save_restore): Declare. (mips16e_save_restore_pattern_p): Likewise. * config/mips/mips.h (GENERATE_MIPS16E_SAVE_RESTORE): New macro. * config/mips/mips.c (MIPS_MAX_FIRST_STACK_STEP): Return 0x7f8 for GENERATE_MIPS16E_SAVE_RESTORE. Return 0x400 for TARGET_MIPS16 && !GENERATE_MIPS16E_SAVE_RESTORE && !TARGET_64BIT. (BITSET_P): New global macro, extracted from... (mips_for_each_saved_reg): ...here. (mips16e_save_restore_info): New struct. (mips16e_s2_s8_regs, mips16e_a0_a3_regs): New variables. (mips16e_save_restore_regs): New variable. (mips_split_plus, mips16e_find_first_register): New functions. (mips16e_mask_registers): New function. (compute_frame_size): Expand the commentary before the function. Enforce the MIPS16e save and restore register range restrictions. Pad the general register save area at the low end. (mips16e_save_restore_reg, mips16e_build_save_restore) (mips16e_save_restore_pattern_p, mips16e_add_register_range) (mips16e_output_save_restore, mips16e_collect_propagate_value) (mips16e_collect_argument_save, mips16e_collect_argument_saves): New functions. (mips_expand_prologue, mips_expand_epilogue): Handle GENERATE_MIPS16E_SAVE_RESTORE. * config/mips/mips.md (*mips16e_save_restore): New pattern. gcc/testsuite/ * gcc.target/mips/save-restore-1.c: New test. * gcc.target/mips/save-restore-2.c: Likewise. * gcc.target/mips/save-restore-3.c: Likewise. * gcc.target/mips/save-restore-4.c: Likewise. From-SVN: r126207 |
||
|---|---|---|
| .. | ||
| ada/acats | ||
| config | ||
| g++.dg | ||
| g++.old-deja | ||
| gcc.c-torture | ||
| gcc.dg | ||
| gcc.misc-tests | ||
| gcc.target | ||
| gcc.test-framework | ||
| gfortran.dg | ||
| gfortran.fortran-torture | ||
| gnat.dg | ||
| lib | ||
| obj-c++.dg | ||
| objc | ||
| objc.dg | ||
| treelang | ||
| ChangeLog | ||
| ChangeLog.ptr | ||
| ChangeLog.tree-ssa | ||
| README | ||
| README.QMTEST | ||
| README.compat | ||
| README.gcc | ||
README
This is a collection of tests for GCC. For further information about the C testsuite, see README.gcc. The driver that runs this testsuite is called DejaGnu and you will need a current DejaGnu snapshot, which is available from ftp://gcc.gnu.org/pub/gcc/infrastructure, for example. These tests are included "as is". If any of them fails, do not report a bug. Bug reports for DejaGnu can go to bug-dejagnu@gnu.org. Discussion and comments about this testsuite should be sent to gcc@gcc.gnu.org; additions and changes to should go to sent to gcc-patches@gcc.gnu.org. The entire testsuite is invoked by `make check` at the top level of the GCC tree. `make check-g++` runs the C++ testsuite only. STRUCTURE OF THE G++ TESTSUITE g++.dg tests: All new tests should be placed in an appropriate subdirectory of g++.dg. g++.old-deja tests: g++.benjamin Tests by Benjamin Koz g++.bob g++.brendan Tests by Brendan Kehoe g++.bugs g++.eh Tests for exception handling g++.ext Tests for g++ extensions g++.gb Tests by Gerald Baumgartner g++.jason Tests by Jason Merill g++.jeff Tests by Jeffrey A Law g++.martin Tests by Martin v. Löwis g++.mike Tests by Mike Stump g++.niklas Tests by Niklas Hallqvist g++.ns Tests for namespaces g++.other g++.pt Tests for templates g++.rfg g++.robertl Tests from gcc-bugs@gcc.gnu.org, gathered by Robert Lipe Finally, some random last minute notes by Mike Stump <mrs@cygnus.com>, on how to run tests (in the GCC 2.7 era): runtest --tool g++ --srcdir ./testsuite where runtest Is the name used to invoke DejaGnu. If DejaGnu is not install this will be the relative path name for runtest. --tool This tells DejaGnu which tool you are testing. It is mainly used to find the testsuite directories for a particular tool when several testsuites are in the same directory. (like the gcc and g++ testsuites) --srcdir This points to the top level of the directory containing the sources of the testsuite. This is ./testsuite if you are in the directory that has the testsuite directory.