diff options
author | Kewen Lin <linkw@linux.ibm.com> | 2023-03-08 00:57:21 -0600 |
---|---|---|
committer | Kewen Lin <linkw@linux.ibm.com> | 2023-03-08 00:57:21 -0600 |
commit | 2a2a159f7bd9d929ce457937f669ed2dd6ebccec (patch) | |
tree | 789b25c3d9492fdc1515835ea4f6e1f741a48b5a /gcc/fold-const.cc | |
parent | 04ff5ad0f32d6736765ad027226367939da7fd0f (diff) | |
download | gcc-2a2a159f7bd9d929ce457937f669ed2dd6ebccec.zip gcc-2a2a159f7bd9d929ce457937f669ed2dd6ebccec.tar.gz gcc-2a2a159f7bd9d929ce457937f669ed2dd6ebccec.tar.bz2 |
testsuite: Adjust powerpc ppc-fortran.exp to support dg-{warning,error}
According to Haochen's finding in [1], currently ppc-fortran.exp
doesn't support Fortran specific warning or error messages well.
By looking into it, it's due to that gfortran uses some different
warning/error prefixes as follows:
set gcc_warning_prefix "\[Ww\]arning:"
set gcc_error_prefix "(Fatal )?\[Ee\]rror:"
comparing to:
set gcc_warning_prefix "warning:"
set gcc_error_prefix "(fatal )?error:"
So this is to override these two prefixes and make it support
dg-{warning,error} checks.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613302.html
gcc/testsuite/ChangeLog:
* gcc.target/powerpc/ppc-fortran/ppc-fortran.exp: Override
gcc_{warning,error}_prefix with Fortran specific one used in
gfortran_init.
Diffstat (limited to 'gcc/fold-const.cc')
0 files changed, 0 insertions, 0 deletions