public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [testsuite] [arm/aarch64] -fno-short-enums for auto-init-[12].c
Date: Thu,  1 Dec 2022 07:39:58 +0000 (GMT)	[thread overview]
Message-ID: <20221201073958.3B11C3857803@sourceware.org> (raw)

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

commit c3dea07dfda1172381a3b99efc00ad2bf042533a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Dec 1 04:38:46 2022 -0300

    [testsuite] [arm/aarch64] -fno-short-enums for auto-init-[12].c
    
    On arm-eabi, and possibly on other platforms, -fshort-enums is enabled
    by default, which breaks some tests' expectations as to enum sizes
    with DEFERRED_INIT.  Disable short enums so that the expectations are
    met.
    
    
    for  gcc/testsuite/ChangeLog
    
            * c-c++-common/auto-init-1.c: Add -fno-short-enums.
            * c-c++-common/auto-init-2.c: Likewise.
    
    
    Change-Id: Ia07e607fe349cb4e0b7178f979e6cb07289c3a48
    TN: VB12-010

Diff:
---
 gcc/testsuite/c-c++-common/auto-init-1.c | 2 +-
 gcc/testsuite/c-c++-common/auto-init-2.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/c-c++-common/auto-init-1.c b/gcc/testsuite/c-c++-common/auto-init-1.c
index df04358728b..3e6a4984eea 100644
--- a/gcc/testsuite/c-c++-common/auto-init-1.c
+++ b/gcc/testsuite/c-c++-common/auto-init-1.c
@@ -1,6 +1,6 @@
 /* Verify zero initialization for integer and pointer type automatic variables.  */
 /* { dg-do compile { target { ilp32 || lp64 } } } */
-/* { dg-options "-ftrivial-auto-var-init=zero -fdump-tree-gimple" } */
+/* { dg-options "-ftrivial-auto-var-init=zero -fno-short-enums -fdump-tree-gimple" } */
 
 #ifndef __cplusplus
 # define bool _Bool
diff --git a/gcc/testsuite/c-c++-common/auto-init-2.c b/gcc/testsuite/c-c++-common/auto-init-2.c
index 6ac63bb1dda..d356e508b83 100644
--- a/gcc/testsuite/c-c++-common/auto-init-2.c
+++ b/gcc/testsuite/c-c++-common/auto-init-2.c
@@ -1,6 +1,6 @@
 /* Verify pattern initialization for integer and pointer type automatic variables.  */
 /* { dg-do compile { target { ilp32 || lp64 } } } */
-/* { dg-options "-ftrivial-auto-var-init=pattern -fdump-tree-gimple" } */
+/* { dg-options "-ftrivial-auto-var-init=pattern -fno-short-enums -fdump-tree-gimple" } */
 
 #ifndef __cplusplus
 # define bool _Bool

             reply	other threads:[~2022-12-01  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  7:39 Alexandre Oliva [this message]
2022-12-03  7:32 Alexandre Oliva

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=20221201073958.3B11C3857803@sourceware.org \
    --to=aoliva@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).