public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/115294] New: [15 regression] dg-additional-files-options change broke several testsuites
Date: Thu, 30 May 2024 19:26:09 +0000	[thread overview]
Message-ID: <bug-115294-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115294
           Summary: [15 regression] dg-additional-files-options change
                    broke several testsuites
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: aoliva at gcc dot gnu.org
  Target Milestone: ---

Between 20240529 (18f477980c8597fe3dca2c2e8bd533c0c2b17aa6) and 20240530
(71899d6b4e18145f005046681208db0137c95ede),
several testsuite results were lost completely.

libatomic, libgomp, libitm, and libphobos are affected.  In each case, the
test logs show a variation of

ERROR: tcl error sourcing
/vol/gcc/src/hg/master/local/libatomic/testsuite/../../gcc/testsuite/lib/gcc-dg.exp.
wrong # args: should be "dg-additional-files-options options source dest type"
    while executing
"check_cached_effective_target $prop {
        eval [list check_no_compiler_messages_nocache $prop] $args
    }"
    (procedure "check_no_compiler_messages" line 2)
    invoked from within
"check_no_compiler_messages lto object {
       void foo (void) { }
    } "-flto""
    (procedure "check_effective_target_lto" line 11)
    invoked from within
"check_effective_target_lto"
    invoked from within
"if [info exists TORTURE_OPTIONS] {
    set DG_TORTURE_OPTIONS $TORTURE_OPTIONS
} else {
    # It is theoretically beneficial to group all of the O2/O3..."
    (file
"/vol/gcc/src/hg/master/local/libatomic/testsuite/../../gcc/testsuite/lib/gcc-dg.exp"
line 82)
    invoked from within
"source
/vol/gcc/src/hg/master/local/libatomic/testsuite/../../gcc/testsuite/lib/gcc-dg.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/vol/gcc/src/hg/master/local/libatomic/testsuite/../../gcc/testsuite/lib/gcc-dg.exp"
    invoked from within
"catch "uplevel #0 source $file""

I'm seeing this on both i386-pc-solaris2.11 and x86_64-pc-linux-gnu; most
likely
this happens everywhere.

             reply	other threads:[~2024-05-30 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 19:26 ro at gcc dot gnu.org [this message]
2024-05-30 19:26 ` [Bug testsuite/115294] " ro at gcc dot gnu.org
2024-05-31  6:46 ` rguenth at gcc dot gnu.org
2024-05-31  6:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-31  7:30 ` cvs-commit at gcc dot gnu.org
2024-05-31  7:32 ` ro 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-115294-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).