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 tree-optimization/104730] New: gcc.dg/vect/complex/pr102819-9.c FAILs
Date: Tue, 01 Mar 2022 10:34:42 +0000	[thread overview]
Message-ID: <bug-104730-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104730
           Summary: gcc.dg/vect/complex/pr102819-9.c FAILs
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: tnfchris at gcc dot gnu.org
  Target Milestone: ---
            Target: sparc*-sun-solaris2.11

The new gcc.dg/vect/complex/pr102819-9.c test FAILs on SPARC (both 32 and
64-bit)
since its introduction:

+FAIL: gcc.dg/vect/complex/pr102819-9.c -flto -ffat-lto-objects  scan-tree-dump
vect "Found COMPLEX_FMS"
+FAIL: gcc.dg/vect/complex/pr102819-9.c scan-tree-dump vect "Found COMPLEX_FMS"

I'm attaching the dump.

             reply	other threads:[~2022-03-01 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 10:34 ro at gcc dot gnu.org [this message]
2022-03-01 10:36 ` [Bug tree-optimization/104730] " ro at gcc dot gnu.org
2022-03-01 10:36 ` ro at gcc dot gnu.org
2022-03-01 10:40 ` [Bug testsuite/104730] " tnfchris at gcc dot gnu.org
2022-03-01 13:58 ` rguenth at gcc dot gnu.org
2022-03-02 12:51 ` cvs-commit at gcc dot gnu.org
2022-03-02 12:55 ` cvs-commit at gcc dot gnu.org
2022-03-02 12:57 ` tnfchris 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-104730-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).