public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/65116] additional_sources not defined anymore during dg-final
Date: Thu, 19 Feb 2015 10:09:00 -0000	[thread overview]
Message-ID: <bug-65116-4-14vln65qAM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65116-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65116

--- Comment #1 from vries at gcc dot gnu.org ---
Presumably same thing happens for pr47218.C, which saves temps:
...
/* { dg-options "-save-temps" } */
...

And cleans them up:
...
// { dg-final { cleanup-saved-temps } 
...

but also has additional sources:
...
/* { dg-additional-sources "pr47218-1.C" } */
...

Of which the temps are not cleaned up:
...
pr47218-1.o pr47218-1.ii pr47218-1.s
...


  reply	other threads:[~2015-02-19 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  9:58 [Bug testsuite/65116] New: " vries at gcc dot gnu.org
2015-02-19 10:09 ` vries at gcc dot gnu.org [this message]
2015-02-19 12:02 ` [Bug testsuite/65116] " redi at gcc dot gnu.org
2015-02-19 12:09 ` vries at gcc dot gnu.org
2015-02-19 12:11 ` [Bug testsuite/65116] [4.9/5 Regression] " rguenth at gcc dot gnu.org
2015-02-19 12:13 ` mkuvyrkov at gcc dot gnu.org
2015-02-19 12:30 ` vries at gcc dot gnu.org
2015-02-19 18:13 ` dje at gcc dot gnu.org
2015-02-19 19:43 ` vries at gcc dot gnu.org
2015-02-19 19:58 ` mkuvyrkov at gcc dot gnu.org
2015-02-19 20:05 ` mkuvyrkov at gcc dot gnu.org
2015-02-19 23:35 ` [Bug testsuite/65116] [4.9/5 Regression] ERROR: can't read additional_sources: no such variable vries at gcc dot gnu.org
2015-03-24 17:28 ` mkuvyrkov at gcc dot gnu.org

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=bug-65116-4-14vln65qAM@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).