On 12/2/24 4:41 PM, Jakub Jelinek wrote:
On Mon, Dec 02, 2024 at 04:37:22PM -0700, Jeff Law wrote:
and similarly for all other crc-side-instr*.c
These tests are clearly written for gcc.dg/torture/, but placed in gcc.dg/,
where we don't cycle through different options and none of explicit -O0,
-O1, -Os or -flto will be among the options, only -fdump-tree-crc-details
will be and so it will be compiled without optimizations and
all the scan-tree-dump directives UNRESOLVED because crc dump doesn't exist
at -O0.
There were a few more with a different naming convention, but right now it
looks like they'll all move into torture/ without triggering any new
fallout.
Yes,
+UNRESOLVED: gcc.dg/crc-linux-1.c scan-tree-dump crc "calculates CRC!"
+UNRESOLVED: gcc.dg/crc-linux-2.c scan-tree-dump crc "calculates CRC!"
+UNRESOLVED: gcc.dg/crc-linux-5.c scan-tree-dump crc "drm_dp_msg_data_crc4 function
maybe contains CRC calculation."
+UNRESOLVED: gcc.dg/crc-not-crc-15.c scan-tree-dump-times crc "calculates CRC!" 0
is what I see on i686-linux.
Same ones I found with a grep.
jeff
