Hi Bernd, hi all,
note that you can get even more files: If you do offloading,
LTO is additionally run for each offloading target (there
can be more than one), cf. https://gcc.gnu.org/wiki/Offloading
Some of those files are probably also from mkoffload etc.
See below.
On 2/20/20 4:33 PM, Bernd Edlinger wrote:
On 2/20/20 2:34 PM, Richard Biener wrote:
I don't think this is an improvement. The files still
will be (correctly) retained and now in addition to that
there's temporary directories piling up?
Well, the temp. directory has a known name,
in case the command line is
gcc -save-temps -lto -o test test.c
there are those 4 in a *known* place, test.lto_tmpdir:
Here, with offloading (compiler only supports one
offloading target), I get for
gfortran -fopenacc -save-temps -o test kernels-map-2.F90
(1) in the current directory:
kernels-map-2.f90
kernels-map-2.o
test.lto_wrapper_args
kernels-map-2.res
kernels-map-2.s
ccv97orQ.i
ccv97orQ.s
(2) in /tmp:
ccXtFBKP.ofldlist
cckm9TaT
cc1aPJVX
ccwnCSfQ
ccEwCVRX
ccv97orQ.c
ccgtnzbU.mkoffload
ccsZzs01
ccouoZqP.target.o
cc6o87mX.crtoffloadtable.o
test
And with "-flto" in addition:
(1) Current directory:
kernels-map-2.f90
kernels-map-2.o
test.lto_wrapper_args
kernels-map-2.res
kernels-map-2.s
ccdBFFxF.i
ccdBFFxF.s
test.ltrans0.o
test.ltrans.out
test.ltrans0.s
test.ltrans0.ltrans.o
test
(2) in /tmp:
ccX5EDTE.ofldlist
ccpAKbE7
ccxnuNsz
ccq5sdmF
ccWUsloz
ccZ5rev7.mkoffload
ccdBFFxF.c
cc3PGOK1
ccW4hTGF.target.o
ccWH1ft2
ccsKJG3z.crtoffloadtable.o
ccmE0bPK
ccB54fLv
cckO6O6c
Cheers,
Tobias
