[gcc r11-7957] testsuite: Fix up gcc.target/i386/pr99726.c test [PR99726]

[gcc r11-7957] testsuite: Fix up gcc.target/i386/pr99726.c test [PR99726]

[Jakub Jelinek]

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

commit r11-7957-ge53c0696113cced90561e79ade27445f6c0926d0
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 2 10:07:50 2021 +0200

    testsuite: Fix up gcc.target/i386/pr99726.c test [PR99726]
    
    -m32 shouldn't be used in gcc.target/i386/ testcases, people do
    test with -m32/-m64 to get 32-bit compilation tested.
    And, -floop-nest-optimize is a graphite optimization, so might not
    be enabled in all gcc builds.
    
    2021-04-02  Jakub Jelinek  <jakub@redhat.com>
    
            PR tree-optimization/99726
            * gcc.target/i386/pr99726.c: Remove -m32 from dg-options.  Move
            -floop-nest-optimize to dg-additional-options guarded on fgraphite
            effective target.

Diff:
---
 gcc/testsuite/gcc.target/i386/pr99726.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/i386/pr99726.c b/gcc/testsuite/gcc.target/i386/pr99726.c
index ff19bcabe4f..98ccce6a979 100644
--- a/gcc/testsuite/gcc.target/i386/pr99726.c
+++ b/gcc/testsuite/gcc.target/i386/pr99726.c
@@ -1,4 +1,5 @@
-/* { dg-options "-flive-patching=inline-clone -mavx512f -O2 -floop-nest-optimize -ftree-loop-vectorize -ftrapv -m32" } */
+/* { dg-options "-flive-patching=inline-clone -mavx512f -O2 -ftree-loop-vectorize -ftrapv" } */
+/* { dg-additional-options "-floop-nest-optimize" { target fgraphite } } */
 
 extern int a[256][1024];
 int b;