public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	Andrew Stubbs <ams@codesourcery.com>
Subject: Re: [Patch] mkoffload: Cleanup temporary omp_requires_file
Date: Fri, 19 Aug 2022 16:05:59 +0200	[thread overview]
Message-ID: <Yv+Yx0FxP4NlhuB1@tucnak> (raw)
In-Reply-To: <8623b1a3-ef98-1ebb-1abc-194b646288a7@codesourcery.com>

On Fri, Aug 19, 2022 at 04:01:10PM +0200, Tobias Burnus wrote:
> Rather obvious, once found. I forgot to add some cleanup, cluttering
> /tmp with ".mkoffload.omp_requires".
> 
> The same issue exists for GCN also for ".mkoffload.dbg"
> 
> OK for mainline? – For the dbg issue, OK also for GCC 11 and 12 backport?
> 
> Follow-up to the 'OpenMP: Move omp requires checks to libgomp" commit
> https://gcc.gnu.org/r13-1458-g683f11843974f0bdf42f79cdcbb0c2b43c7b81b0
> 
> For GCN, the issues exists since
> https://gcc.gnu.org/r11-6683-g505caa7295b93ecdec8ac9b31595eb34dbd48c9f
> 
> Tobias
> 
> PS: In case you wonder why it is also added with -save-temps: The
> internally called maybe_unlink removed the file, unless -save-temps. For
> the latter, with verbose flag, it also shows them as '[Leaving %s]'.
> 
> PPS: If you see some ...target.o files in /tmp, that's because of
> https://gcc.gnu.org/PR106686
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

> mkoffload: Cleanup temporary omp_requires_file
> 
> The file (suffix ".mkoffload.omp_requires") used to save the 'omp requires'
> data has to be passed to maybe_unlink for cleanup or -v -save-temps stderr
> diagnostic. That was missed before. - For GCN, the same has to be done for
> the files with suffix ".mkoffload.dbg.o".
> 
> gcc/ChangeLog:
> 
> 	* config/gcn/mkoffload.cc (main): Add omp_requires_file and dbgobj to
> 	files_to_cleanup.
> 	* config/i386/intelmic-mkoffload.cc (prepare_target_image): Add
> 	omp_requires_file to temp_files.
> 	* config/nvptx/mkoffload.cc (omp_requires_file): New global static var.
> 	(main): Remove local omp_requires_file var.
> 	(tool_cleanup): Handle omp_requires_file.

Ok, thanks.

	Jakub


      reply	other threads:[~2022-08-19 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 14:01 Tobias Burnus
2022-08-19 14:05 ` Jakub Jelinek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yv+Yx0FxP4NlhuB1@tucnak \
    --to=jakub@redhat.com \
    --cc=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).