public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9041] Add -Wstrict-aliasing to vector-struct-1.C testcase
Date: Fri, 16 Feb 2024 21:58:18 +0000 (GMT)	[thread overview]
Message-ID: <20240216215818.0CD16385782D@sourceware.org> (raw)

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

commit r14-9041-gcd503b0616462445381a8232fb753239d319af76
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Fri Feb 16 13:26:30 2024 -0800

    Add -Wstrict-aliasing to vector-struct-1.C testcase
    
    As noticed by Marek Polacek in https://gcc.gnu.org/pipermail/gcc-patches/2024-February/645836.html,
    this testcase was not failing before without -Wstrict-aliasing so let's add that option.
    
    Committed as obvious after testing to make sure the test is now testing with `-Wstrict-aliasing` and `-flto`.
    
    gcc/testsuite/ChangeLog:
    
            * g++.dg/torture/vector-struct-1.C: Add -Wstrict-aliasing.
    
    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>

Diff:
---
 gcc/testsuite/g++.dg/torture/vector-struct-1.C | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/g++.dg/torture/vector-struct-1.C b/gcc/testsuite/g++.dg/torture/vector-struct-1.C
index e2747417e2d5..969a801e6807 100644
--- a/gcc/testsuite/g++.dg/torture/vector-struct-1.C
+++ b/gcc/testsuite/g++.dg/torture/vector-struct-1.C
@@ -1,3 +1,4 @@
+/* { dg-options "-Wstrict-aliasing" } */
 /* PR c++/97990 */
 /* This used to crash with lto and strict aliasing enabled as the
    vector type variant still had TYPE_ALIAS_SET set on it. */

                 reply	other threads:[~2024-02-16 21:58 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=20240216215818.0CD16385782D@sourceware.org \
    --to=pinskia@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).