public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [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
Date: Tue, 13 Feb 2024 21:52:52 +0000	[thread overview]
Message-ID: <bug-113899-4-yAkuPyIOs0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113899-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I do think there is something wrong with your remote testing too but that
is only slightly related.

check_sse_hw_available should still be returning 1 there since SSE should
always be available for x86_64-linux. You might want to check the full log to
see why check_sse_hw_available is not working.  Maybe it is not picking up the
libraries or something like that.

Maybe the run testcases are failing but you might not be noticing that.

  parent reply	other threads:[~2024-02-13 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  8:37 [Bug testsuite/113899] New: Vect module test failures while running on remote host sadineniharish8446 at gmail dot com
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 [this message]
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-yAkuPyIOs0@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).