public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iverbin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/64605] New: [5 Regression] ERROR: (DejaGnu) proc "libatomic_target_compile lto1738.c lto1738.o object additional_flags=-flto" does not exist.
Date: Wed, 14 Jan 2015 22:12:00 -0000	[thread overview]
Message-ID: <bug-64605-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64605
           Summary: [5 Regression] ERROR: (DejaGnu) proc
                    "libatomic_target_compile lto1738.c lto1738.o object
                    additional_flags=-flto" does not exist.
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: iverbin at gcc dot gnu.org

A fix for check_effective_target_lto (r219606) caused an ERROR in libatomic
testsuite.

To reproduce: make check-target-libatomic

ERROR: (DejaGnu) proc "libatomic_target_compile lto4486.c lto4486.o object
additional_flags=-flto" does not exist.
The error code is NONE
The info on the error is:
invalid command name "libatomic_target_compile"
    while executing
"::tcl_unknown libatomic_target_compile lto4486.c lto4486.o object
additional_flags=-flto"
    ("uplevel" body line 1)
    invoked from within
"uplevel 1 ::tcl_unknown $args"


             reply	other threads:[~2015-01-14 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 22:12 iverbin at gcc dot gnu.org [this message]
2015-01-15  9:28 ` [Bug testsuite/64605] " rguenth at gcc dot gnu.org
2015-01-15 15:39 ` iverbin at gmail dot com
2015-01-16 11:30 ` iverbin at gcc dot gnu.org
2015-01-16 14:56 ` iverbin 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-64605-4@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).