[Bug lto/106686] [lto][offloading] lto-wrapper leaves "target.o" temporay files behind when error diagnostic occurred

2022-08-22 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106686

Tobias Burnus  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #3 from Tobias Burnus  ---
FIXED on GCC 13 (mainline).

[Bug lto/106686] [lto][offloading] lto-wrapper leaves "target.o" temporay files behind when error diagnostic occurred

2022-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106686

--- Comment #2 from CVS Commits  ---
The master branch has been updated by Tobias Burnus :

https://gcc.gnu.org/g:e228683b244c6afbe3bdfef7ba607fbda813bd0f

commit r13-2135-ge228683b244c6afbe3bdfef7ba607fbda813bd0f
Author: Tobias Burnus 
Date:   Mon Aug 22 09:49:52 2022 +0200

lto-wrapper.cc: Delete offload_names temp files in case of error [PR106686]

Usually, the caller takes care of the .o files for the offload compilers
(suffix: ".target.o"). However, if an error occurs during processing
(e.g. fatal error by lto1), they were not deleted.

gcc/ChangeLog:

PR lto/106686
* lto-wrapper.cc (free_array_of_ptrs): Move before tool_cleanup.
(tool_cleanup): Unlink offload_names.
(compile_offload_image): Take filename argument to set it early.
(compile_images_for_offload_targets): Update call; set
offload_names to NULL after freeing the array.

[Bug lto/106686] [lto][offloading] lto-wrapper leaves "target.o" temporay files behind when error diagnostic occurred

2022-08-22 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106686

Martin Liška  changed:

   What|Removed |Added

   Last reconfirmed||2022-08-22
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

[Bug lto/106686] [lto][offloading] lto-wrapper leaves "target.o" temporay files behind when error diagnostic occurred

2022-08-19 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106686

--- Comment #1 from Tobias Burnus  ---
Patch: https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600033.html