public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
Date: Tue, 19 Jul 2022 06:23:40 +0000	[thread overview]
Message-ID: <bug-106345-4-3TehZNgSRQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106345-4@http.gcc.gnu.org/bugzilla/>

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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-07-19
           Assignee|unassigned at gcc dot gnu.org      |linkw at gcc dot gnu.org
     Ever confirmed|0                           |1
                 CC|                            |linkw at gcc dot gnu.org
             Status|UNCONFIRMED                 |ASSIGNED

--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
Thanks for reporting!

For

gcc.target/powerpc/lhs-3.c AND its siblings lhs-{1,2}.c
gcc.target/powerpc/loop_align.c

, they should use (or append) dejagnu-tune since the expected asm requires the
related sched info.

But for gcc.target/powerpc/pr92398.p9-.c, it fails due to one different cause:
the case is guarded with ! has_arch_pwr9, shouldn't tested with p9 setting, but
the previous evaluation failed, see below:

is-effective-target: has_arch_pwr9 0

arch_pwr91035958.c:8: error: ISO C forbids an empty translation unit
[-Wpedantic]

  reply	other threads:[~2022-07-19  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 17:32 [Bug testsuite/106345] New: " mpolacek at gcc dot gnu.org
2022-07-19  6:23 ` linkw at gcc dot gnu.org [this message]
2022-07-20  2:01 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
2022-07-25  5:53 ` cvs-commit at gcc dot gnu.org
2022-07-26 12:13 ` linkw at gcc dot gnu.org
2022-08-02  3:53 ` cvs-commit at gcc dot gnu.org
2022-08-02  3:56 ` cvs-commit at gcc dot gnu.org
2022-08-02  3:58 ` cvs-commit at gcc dot gnu.org
2022-09-07  1:38 ` cvs-commit at gcc dot gnu.org
2022-09-13  5:21 ` cvs-commit at gcc dot gnu.org
2022-09-13  5:22 ` cvs-commit at gcc dot gnu.org
2022-09-13  6:23 ` cvs-commit at gcc dot gnu.org
2022-09-13  6:24 ` linkw 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-106345-4-3TehZNgSRQ@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).