public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sadineniharish8446 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113899] New: Vect module test failures while running on remote host
Date: Tue, 13 Feb 2024 08:37:30 +0000	[thread overview]
Message-ID: <bug-113899-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113899
           Summary: Vect module test failures while running on remote host
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sadineniharish8446 at gmail dot com
  Target Milestone: ---

We've seen a few test failures on gcc vect module, while running gcc testsuite
on Yocto framework for the custom target with Remote host testing via ssh .
Below is the error message,
         xgcc: fatal error: cannot specify '-o' with '-c', '-S' or '-E' with
multiple files
         compilation terminated.
         compiler exited with status 1
         FAIL: gcc.dg/vect/vect-simd-clone-12.c -flto -ffat-lto-objects (test
for excess errors)
         Excess errors:
         xgcc: fatal error: cannot specify '-o' with '-c', '-S' or '-E' with
multiple files
         compilation terminated

Below is the cmd causing the error:
/poky/build2-st/tmp/work/core2-64-poky-linux/gcc-runtime/13.2.0/gcc-13.2.0/build.x86_64-poky-linux.x86_64-poky-linux/gcc/xgcc
-B/poky/build2-st/tmp/work/core2-64-poky-linux/gcc-runtime/13.2.0/gcc-13.2.0/build.x86_64-poky-linux.x86_64-poky-linux/gcc/

/poky/build2-st/tmp/work-shared/gcc-13.2.0-r0/gcc-13.2.0/gcc/testsuite/gcc.dg/vect/vect-simd-clone-12.c
   
--sysroot=/poky/build2-st/tmp/work/core2-64-poky-linux/gcc-runtime/13.2.0/recipe-sysroot
-fdiagnostics-plain-output
--sysroot=/poky/build2-st/tmp/work/core2-64-poky-linux/gcc-runtime/13.2.0/recipe-sysroot
 -msse2 -ftree-vectorize -fno-tree-loop-distribute-patterns
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -fopenmp-simd 
/poky/build2-st/tmp/work-shared/gcc-13.2.0-r0/gcc-13.2.0/gcc/testsuite/gcc.dg/vect/vect-simd-clone-12a.c
-dumpbase "" -S -o vect-simd-clone-12.s 
There are two .c files (vect-simd-clone-12.c & vect-simd-clone-12a.c) are
passed to test case.

As per our analysis,
- When the test suite executed on host machine (w/o Remote host testing), the
'-o' option is passed with .exe file as output (eg: -dumpbase "" -o
vect-simd-clone-12.exe ). In this case, the two .c files are compiled and .exe
is generating and no issues with test execution.
- In remote tesing with ssh, there is an additional '-S' option is passed with
"-o vect-simd-clone-12.s" (See above given test command), here the compiler is
trying to compile both .c files and forced to create a single assembly file as
output and fails with below error.
xgcc: fatal error: cannot specify '-o' with '-c', '-S' or '-E' with multiple
files

This might be a bug in test suite when doing remote testing.
Please confirm the issue and let us know if any further inputs needed.

             reply	other threads:[~2024-02-13  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  8:37 sadineniharish8446 at gmail dot com [this message]
2024-02-13 21:04 ` [Bug testsuite/113899] Vect module test failures while running on remote host due to default dg-do set to compile and additional-sources being used pinskia at gcc dot gnu.org
2024-02-13 21:46 ` pinskia at gcc dot gnu.org
2024-02-13 21:52 ` pinskia at gcc dot gnu.org
2024-02-14 13:41 ` cvs-commit at gcc dot gnu.org
2024-02-14 13:42 ` pinskia at gcc dot gnu.org
2024-02-15  8:55 ` sadineniharish8446 at gmail dot com
2024-02-15  9:05 ` pinskia 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-113899-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).