public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-8365] LoongArch: testsuite: Disable stack protector for got-load.C
Date: Tue, 23 Jan 2024 15:45:16 +0000 (GMT)	[thread overview]
Message-ID: <20240123154516.8887F3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:46f3ba56c47f002153d23334348dadea206dae79

commit r14-8365-g46f3ba56c47f002153d23334348dadea206dae79
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Tue Jan 23 19:32:38 2024 +0800

    LoongArch: testsuite: Disable stack protector for got-load.C
    
    When building GCC with --enable-default-ssp, the stack protector is
    enabled for got-load.C, causing additional GOT loads for
    __stack_chk_guard.  So mem/u will be matched more than 2 times and the
    test will fail.
    
    Disable stack protector to fix this issue.
    
    gcc/testsuite:
    
            * g++.target/loongarch/got-load.C (dg-options): Add
            -fno-stack-protector.

Diff:
---
 gcc/testsuite/g++.target/loongarch/got-load.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.target/loongarch/got-load.C b/gcc/testsuite/g++.target/loongarch/got-load.C
index 20924c73942..17870176ab4 100644
--- a/gcc/testsuite/g++.target/loongarch/got-load.C
+++ b/gcc/testsuite/g++.target/loongarch/got-load.C
@@ -1,5 +1,5 @@
 /* { dg-do compile } */
-/* { dg-options "-mabi=lp64d -O2 -mexplicit-relocs -mcmodel=normal -fdump-rtl-expand" } */
+/* { dg-options "-mabi=lp64d -O2 -mexplicit-relocs -mcmodel=normal -fdump-rtl-expand -fno-stack-protector" } */
 /* { dg-final { scan-rtl-dump-times "mem/u" 2 "expand" } } */
 
 #include <bits/stdc++.h>

                 reply	other threads:[~2024-01-23 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240123154516.8887F3858D3C@sourceware.org \
    --to=xry111@gcc.gnu.org \
    --cc=gcc-cvs@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).