aboutsummaryrefslogtreecommitdiff
path: root/gcc/diagnostic-format-json.cc
diff options
context:
space:
mode:
authorPan Li <pan2.li@intel.com>2024-06-17 09:31:33 +0800
committerPan Li <pan2.li@intel.com>2024-06-18 21:44:50 +0800
commite4f938936867d8799775d1455e67bd3fb8711afd (patch)
treeb6c70daba54b1fae9eb459eccd5100a54f02d0e1 /gcc/diagnostic-format-json.cc
parent9b109826e0b0473572395f5837b455d57fa5a93c (diff)
downloadgcc-e4f938936867d8799775d1455e67bd3fb8711afd.zip
gcc-e4f938936867d8799775d1455e67bd3fb8711afd.tar.gz
gcc-e4f938936867d8799775d1455e67bd3fb8711afd.tar.bz2
Match: Support forms 7 and 8 for the unsigned .SAT_ADD
When investigate the vectorization of .SAT_ADD, we notice there are additional 2 forms, aka form 7 and 8 for .SAT_ADD. Form 7: #define DEF_SAT_U_ADD_FMT_7(T) \ T __attribute__((noinline)) \ sat_u_add_##T##_fmt_7 (T x, T y) \ { \ return x > (T)(x + y) ? -1 : (x + y); \ } Form 8: #define DEF_SAT_U_ADD_FMT_8(T) \ T __attribute__((noinline)) \ sat_u_add_##T##_fmt_8 (T x, T y) \ { \ return x <= (T)(x + y) ? (x + y) : -1; \ } Thus, add above 2 forms to the match gimple_unsigned_integer_sat_add, and then the vectorizer can try to recog the pattern like form 7 and form 8. The below test suites are passed for this patch: 1. The rv64gcv fully regression test with newlib. 2. The rv64gcv build with glibc. 3. The x86 bootstrap test. 4. The x86 fully regression test. gcc/ChangeLog: * match.pd: Add form 7 and 8 for the unsigned .SAT_ADD match. Signed-off-by: Pan Li <pan2.li@intel.com>
Diffstat (limited to 'gcc/diagnostic-format-json.cc')
0 files changed, 0 insertions, 0 deletions