aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.h
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2023-04-28 08:53:00 +0200
committerJan Beulich <jbeulich@suse.com>2023-04-28 08:53:00 +0200
commitd76c343d6a6295a8cc612fc19a99156aa0976180 (patch)
tree58291257efc19c37de453d078c3862bb96123d83 /gcc/value-range.h
parent9be54d6abad76b0d7f227687bf6b296e562d89fb (diff)
downloadgcc-d76c343d6a6295a8cc612fc19a99156aa0976180.zip
gcc-d76c343d6a6295a8cc612fc19a99156aa0976180.tar.gz
gcc-d76c343d6a6295a8cc612fc19a99156aa0976180.tar.bz2
testsuite/C++: suppress filename canonicalization in module tests
The pathname underneath gcm.cache/ is determined from the effective name used for the main input file of a particular module. When modules are built, no canonicalization occurs for the main input file. Hence the module file wouldn't be found if a different (the canonicalized) file name was used when importing that same module. (This is an effect of importing happening in the preprocessor, just like #include handling.) Since it doesn't look easy to make module generation use libcpp's maybe_shorter_path() (in fact I'd consider this a layering violation, while cloning the logic would - at least in principle - be prone to both going out of sync), simply suppress system header path canonicalization for the respective tests. gcc/testsuite/ * g++.dg/modules/alias-1_b.C: Add -fno-canonical-system-headers. * g++.dg/modules/alias-1_d.C: Likewise. * g++.dg/modules/alias-1_e.C: Likewise. * g++.dg/modules/alias-1_f.C: Likewise. * g++.dg/modules/cpp-6_c.C: Likewise. * g++.dg/modules/dir-only-2_b.C: Likewise.
Diffstat (limited to 'gcc/value-range.h')
0 files changed, 0 insertions, 0 deletions