Fix test_scan_layouts[True-1-src_layout10-64-32] on LTS driver

[anmyachev]

No description provided.

[anmyachev]

@whitneywhtsang this test produces many of the same constants, such as:

@assertFunc_447 = internal addrspace(1) constant [8 x i8] c"unknown\00"
@assertFile_447 = internal addrspace(1) constant [87 x i8] c".../pytest-0/test_scan_layouts_True_1_src_l0/test_scan_layouts.ttgir\00"
@assertMessage_447 = internal addrspace(1) constant [18 x i8] c"overflow detected\00"

Does it make sense to compare the contents of constants before adding them to reduce their total number? If so, I would like to try to implement it.

[whitneywhtsang]

@whitneywhtsang this test produces many of the same constants, such as:

@assertFunc_447 = internal addrspace(1) constant [8 x i8] c"unknown\00"
@assertFile_447 = internal addrspace(1) constant [87 x i8] c".../pytest-0/test_scan_layouts_True_1_src_l0/test_scan_layouts.ttgir\00"
@assertMessage_447 = internal addrspace(1) constant [18 x i8] c"overflow detected\00"

Does it make sense to compare the contents of constants before adding them to reduce their total number? If so, I would like to try to implement it.

Is it related to the test failure? Is it unique to Intel backend?

[anmyachev]

Is it related to the test failure?

Not directly, I just noticed that there were a lot of identical objects.

Is it unique to Intel backend?

The code is similar to the one used for the NVIDIA backend, I suppose so, but I haven't run it on their hardware.