public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9
@ 2022-07-18 17:32 mpolacek at gcc dot gnu.org
  2022-07-19  6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
                   ` (11 more replies)
  0 siblings, 12 replies; 13+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2022-07-18 17:32 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 106345
           Summary: Some ppc64le tests fail with -mcpu=power9
                    -mtune=power9
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpolacek at gcc dot gnu.org
  Target Milestone: ---

A few tests fail when GCC is configured with --with-cpu-64=power9
--with-tune-64=power9:

gcc.target/powerpc/lhs-3.c
gcc.target/powerpc/loop_align.c
gcc.target/powerpc/pr92398.p9-.c

It would be nice if we could strengthen the tests to pass with -mtune=power9
-mcpu=power9 too.

In detail:

# gcc -O2 -mdejagnu-cpu=power7 lhs-3.c -S -mtune=power8
# grep ori lhs-3.s
        ori 2,2,0

but with the power9 default:

# gcc -O2 -mdejagnu-cpu=power7 lhs-3.c -S
# grep ori lhs-3.s
#

The second:

# gcc loop_align.c -fdiagnostics-plain-output -O2 -mdejagnu-cpu=power7
-falign-functions=16 -fno-unroll-loops -ffat-lto-objects -fno-ident -S -o
loop_align.s
# grep p2align loop_align.s
        .p2align 4,,15
        .p2align 4,,15
# gcc loop_align.c -fdiagnostics-plain-output -O2 -mdejagnu-cpu=power7
-falign-functions=16 -fno-unroll-loops -ffat-lto-objects -fno-ident -S -o
loop_align.s -mtune=power8
# grep p2align loop_align.s
        .p2align 4,,15
        .p2align 5

And the third test:

# gcc pr92398.p9-.c -fdiagnostics-plain-output -O2 -mvsx -ffat-lto-objects
-fno-ident -S -o pr92398.p9-.s -mtune=power8 -mcpu=power8
# grep -E '(std|not)' pr92398.p9-.s
        not 4,4
        not 5,5
        std 4,0(3)
        std 5,8(3)
        .section        .note.GNU-stack,"",@progbits
# gcc pr92398.p9-.c -fdiagnostics-plain-output -O2 -mvsx -ffat-lto-objects
-fno-ident -S -o pr92398.p9-.s 
# grep -E '(std|not)' pr92398.p9-.s
        .section        .note.GNU-stack,"",@progbits

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
@ 2022-07-19  6:23 ` linkw at gcc dot gnu.org
  2022-07-20  2:01 ` linkw at gcc dot gnu.org
                   ` (10 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: linkw at gcc dot gnu.org @ 2022-07-19  6:23 UTC (permalink / raw)
  To: gcc-bugs

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]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
  2022-07-19  6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
@ 2022-07-20  2:01 ` linkw at gcc dot gnu.org
  2022-07-25  5:53 ` cvs-commit at gcc dot gnu.org
                   ` (9 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: linkw at gcc dot gnu.org @ 2022-07-20  2:01 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> ---
Two more failures related to required tuning setting:

PASS->FAIL: gcc.target/powerpc/compress-float-ppc.c scan-assembler lfs
PASS->FAIL: gcc.target/powerpc/compress-float-ppc-pic.c scan-assembler lfs

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
  2022-07-19  6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
  2022-07-20  2:01 ` 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
                   ` (8 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-07-25  5:53 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:75d20d6c84c12bedd65a904e462f02f0b9eb3f77

commit r13-1818-g75d20d6c84c12bedd65a904e462f02f0b9eb3f77
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Mon Jul 25 00:51:44 2022 -0500

    rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345]

    As PR106345 shows, when configuring compiler with an explicit
    option --with-tune=<value>, it would cause some test cases to
    fail if their test points are sensitive to tune setting, such
    as: group_ending_nop, loop align etc.  It doesn't help that
    even to specify one explicit -mcpu=.

    This patch is to adjust the behavior of -mdejagnu-cpu by
    filtering out all -mcpu= and -mtune= options, then test cases
    would use <cpu> as tune as the one specified by -mdejagnu-cpu.

    2022-07-25  Peter Bergner  <bergner@linux.ibm.com>
                Kewen Lin  <linkw@linux.ibm.com>

            PR testsuite/106345

    gcc/ChangeLog:

            * config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu
            to filter out all -mtune options.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  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
                   ` (7 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: linkw at gcc dot gnu.org @ 2022-07-26 12:13 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |seurer at gcc dot gnu.org

--- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> ---
*** Bug 105427 has been marked as a duplicate of this bug. ***

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (3 preceding siblings ...)
  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
                   ` (6 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-08-02  3:53 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:a221c4b8e581d89c311f58c7c2e64c9d1f16c642

commit r10-10925-ga221c4b8e581d89c311f58c7c2e64c9d1f16c642
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Mon Jul 25 00:51:44 2022 -0500

    rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345]

    As PR106345 shows, when configuring compiler with an explicit
    option --with-tune=<value>, it would cause some test cases to
    fail if their test points are sensitive to tune setting, such
    as: group_ending_nop, loop align etc.  It doesn't help that
    even to specify one explicit -mcpu=.

    This patch is to adjust the behavior of -mdejagnu-cpu by
    filtering out all -mcpu= and -mtune= options, then test cases
    would use <cpu> as tune as the one specified by -mdejagnu-cpu.

    2022-07-25  Peter Bergner  <bergner@linux.ibm.com>
                Kewen Lin  <linkw@linux.ibm.com>

            PR testsuite/106345

    gcc/ChangeLog:

            * config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu
            to filter out all -mtune options.

    (cherry picked from commit 75d20d6c84c12bedd65a904e462f02f0b9eb3f77)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (4 preceding siblings ...)
  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
                   ` (5 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-08-02  3:56 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:ab1d329cb7d5ef19d234c37892c3268f063cf9c5

commit r11-10187-gab1d329cb7d5ef19d234c37892c3268f063cf9c5
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Mon Jul 25 00:51:44 2022 -0500

    rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345]

    As PR106345 shows, when configuring compiler with an explicit
    option --with-tune=<value>, it would cause some test cases to
    fail if their test points are sensitive to tune setting, such
    as: group_ending_nop, loop align etc.  It doesn't help that
    even to specify one explicit -mcpu=.

    This patch is to adjust the behavior of -mdejagnu-cpu by
    filtering out all -mcpu= and -mtune= options, then test cases
    would use <cpu> as tune as the one specified by -mdejagnu-cpu.

    2022-07-25  Peter Bergner  <bergner@linux.ibm.com>
                Kewen Lin  <linkw@linux.ibm.com>

            PR testsuite/106345

    gcc/ChangeLog:

            * config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu
            to filter out all -mtune options.

    (cherry picked from commit 75d20d6c84c12bedd65a904e462f02f0b9eb3f77)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (5 preceding siblings ...)
  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
                   ` (4 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-08-02  3:58 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:5f583aa1c56af983ca8f2b8bc57122c4be5a6e55

commit r12-8651-g5f583aa1c56af983ca8f2b8bc57122c4be5a6e55
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Mon Jul 25 00:51:44 2022 -0500

    rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345]

    As PR106345 shows, when configuring compiler with an explicit
    option --with-tune=<value>, it would cause some test cases to
    fail if their test points are sensitive to tune setting, such
    as: group_ending_nop, loop align etc.  It doesn't help that
    even to specify one explicit -mcpu=.

    This patch is to adjust the behavior of -mdejagnu-cpu by
    filtering out all -mcpu= and -mtune= options, then test cases
    would use <cpu> as tune as the one specified by -mdejagnu-cpu.

    2022-07-25  Peter Bergner  <bergner@linux.ibm.com>
                Kewen Lin  <linkw@linux.ibm.com>

            PR testsuite/106345

    gcc/ChangeLog:

            * config/rs6000/rs6000.h (DRIVER_SELF_SPECS): Adjust -mdejagnu-cpu
            to filter out all -mtune options.

    (cherry picked from commit 75d20d6c84c12bedd65a904e462f02f0b9eb3f77)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (6 preceding siblings ...)
  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
                   ` (3 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-09-07  1:38 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:7a43e52a48b6403a99d3e8ab3105869b4b3c081e

commit r13-2504-g7a43e52a48b6403a99d3e8ab3105869b4b3c081e
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Tue Sep 6 20:37:57 2022 -0500

    rs6000/test: Fix empty TU in some cases of effective targets [PR106345]

    As the failure of test case gcc.target/powerpc/pr92398.p9-.c in
    PR106345 shows, some test sources for some powerpc effective
    targets use empty translation unit wrongly.  The test sources
    could go with options like "-ansi -pedantic-errors", then those
    effective target checkings will fail unexpectedly with the
    error messages like:

      error: ISO C forbids an empty translation unit [-Wpedantic]

    This patch is to fix empty TUs with one dummy function definition
    accordingly.

            PR testsuite/106345

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_powerpc_sqrt):
Add
            a function definition to avoid pedwarn about empty translation
unit.
            (check_effective_target_has_arch_pwr5): Likewise.
            (check_effective_target_has_arch_pwr6): Likewise.
            (check_effective_target_has_arch_pwr7): Likewise.
            (check_effective_target_has_arch_pwr8): Likewise.
            (check_effective_target_has_arch_pwr9): Likewise.
            (check_effective_target_has_arch_pwr10): Likewise.
            (check_effective_target_has_arch_ppc64): Likewise.
            (check_effective_target_ppc_float128): Likewise.
            (check_effective_target_ppc_float128_insns): Likewise.
            (check_effective_target_powerpc_vsx): Likewise.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (7 preceding siblings ...)
  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
                   ` (2 subsequent siblings)
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-09-13  5:21 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:19e217a2b9d08508203b6e645b67ab63b17af5f8

commit r12-8761-g19e217a2b9d08508203b6e645b67ab63b17af5f8
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Tue Sep 6 20:37:57 2022 -0500

    rs6000/test: Fix empty TU in some cases of effective targets [PR106345]

    As the failure of test case gcc.target/powerpc/pr92398.p9-.c in
    PR106345 shows, some test sources for some powerpc effective
    targets use empty translation unit wrongly.  The test sources
    could go with options like "-ansi -pedantic-errors", then those
    effective target checkings will fail unexpectedly with the
    error messages like:

      error: ISO C forbids an empty translation unit [-Wpedantic]

    This patch is to fix empty TUs with one dummy function definition
    accordingly.

            PR testsuite/106345

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_powerpc_sqrt):
Add
            a function definition to avoid pedwarn about empty translation
unit.
            (check_effective_target_has_arch_pwr5): Likewise.
            (check_effective_target_has_arch_pwr6): Likewise.
            (check_effective_target_has_arch_pwr7): Likewise.
            (check_effective_target_has_arch_pwr8): Likewise.
            (check_effective_target_has_arch_pwr9): Likewise.
            (check_effective_target_has_arch_pwr10): Likewise.
            (check_effective_target_has_arch_ppc64): Likewise.
            (check_effective_target_ppc_float128): Likewise.
            (check_effective_target_ppc_float128_insns): Likewise.
            (check_effective_target_powerpc_vsx): Likewise.

    (cherry picked from commit 7a43e52a48b6403a99d3e8ab3105869b4b3c081e)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (8 preceding siblings ...)
  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
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-09-13  5:22 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:5cb02a5f803d522cfdc8a517ae9afef4d65353f8

commit r11-10253-g5cb02a5f803d522cfdc8a517ae9afef4d65353f8
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Tue Sep 6 20:37:57 2022 -0500

    rs6000/test: Fix empty TU in some cases of effective targets [PR106345]

    As the failure of test case gcc.target/powerpc/pr92398.p9-.c in
    PR106345 shows, some test sources for some powerpc effective
    targets use empty translation unit wrongly.  The test sources
    could go with options like "-ansi -pedantic-errors", then those
    effective target checkings will fail unexpectedly with the
    error messages like:

      error: ISO C forbids an empty translation unit [-Wpedantic]

    This patch is to fix empty TUs with one dummy function definition
    accordingly.

            PR testsuite/106345

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_powerpc_sqrt):
Add
            a function definition to avoid pedwarn about empty translation
unit.
            (check_effective_target_has_arch_pwr5): Likewise.
            (check_effective_target_has_arch_pwr6): Likewise.
            (check_effective_target_has_arch_pwr7): Likewise.
            (check_effective_target_has_arch_pwr8): Likewise.
            (check_effective_target_has_arch_pwr9): Likewise.
            (check_effective_target_has_arch_pwr10): Likewise.
            (check_effective_target_has_arch_ppc64): Likewise.
            (check_effective_target_ppc_float128): Likewise.
            (check_effective_target_ppc_float128_insns): Likewise.
            (check_effective_target_powerpc_vsx): Likewise.

    (cherry picked from commit 7a43e52a48b6403a99d3e8ab3105869b4b3c081e)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (9 preceding siblings ...)
  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
  11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-09-13  6:23 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:12d28957b613d8c9b74e7841d73945025a7f0ccb

commit r10-10982-g12d28957b613d8c9b74e7841d73945025a7f0ccb
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Tue Sep 6 20:37:57 2022 -0500

    rs6000/test: Fix empty TU in some cases of effective targets [PR106345]

    As the failure of test case gcc.target/powerpc/pr92398.p9-.c in
    PR106345 shows, some test sources for some powerpc effective
    targets use empty translation unit wrongly.  The test sources
    could go with options like "-ansi -pedantic-errors", then those
    effective target checkings will fail unexpectedly with the
    error messages like:

      error: ISO C forbids an empty translation unit [-Wpedantic]

    This patch is to fix empty TUs with one dummy function definition
    accordingly.

            PR testsuite/106345

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_has_arch_pwr5):
Add
            a function definition to avoid pedwarn about empty translation
unit.
            (check_effective_target_has_arch_pwr6): Likewise.
            (check_effective_target_has_arch_pwr7): Likewise.
            (check_effective_target_has_arch_pwr8): Likewise.
            (check_effective_target_has_arch_pwr9): Likewise.
            (check_effective_target_has_arch_ppc64): Likewise.
            (check_effective_target_ppc_float128): Likewise.
            (check_effective_target_ppc_float128_insns): Likewise.
            (check_effective_target_powerpc_vsx): Likewise.

    (cherry picked from commit 7a43e52a48b6403a99d3e8ab3105869b4b3c081e)

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
  2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
                   ` (10 preceding siblings ...)
  2022-09-13  6:23 ` cvs-commit at gcc dot gnu.org
@ 2022-09-13  6:24 ` linkw at gcc dot gnu.org
  11 siblings, 0 replies; 13+ messages in thread
From: linkw at gcc dot gnu.org @ 2022-09-13  6:24 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #14 from Kewen Lin <linkw at gcc dot gnu.org> ---
Should be fixed everywhere.

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2022-09-13  6:24 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-18 17:32 [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 mpolacek at gcc dot gnu.org
2022-07-19  6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
2022-07-20  2:01 ` 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

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).