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)] Drop need for constant I in ctf test
Date: Thu, 16 Feb 2023 11:12:45 +0000 (GMT)	[thread overview]
Message-ID: <20230216111245.C1B893858031@sourceware.org> (raw)

https://gcc.gnu.org/g:87b355ad7d5e70bb3163fb8565a334d5d2bffd96

commit 87b355ad7d5e70bb3163fb8565a334d5d2bffd96
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 16 06:52:12 2023 -0300

    Drop need for constant I in ctf test
    
    Though I is supposed to be a constant expression, this is not the case
    on vxworks, but this is not what this debug information format test is
    testing for, so use real constants to initialize complex variables.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/debug/ctf/ctf-complex-1.c: Do not test whether I is
            usable in initializers.

Diff:
---
 gcc/testsuite/gcc.dg/debug/ctf/ctf-complex-1.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/debug/ctf/ctf-complex-1.c b/gcc/testsuite/gcc.dg/debug/ctf/ctf-complex-1.c
index a36dd9b6b90..e6c3199f913 100644
--- a/gcc/testsuite/gcc.dg/debug/ctf/ctf-complex-1.c
+++ b/gcc/testsuite/gcc.dg/debug/ctf/ctf-complex-1.c
@@ -14,8 +14,8 @@
 
 #include <complex.h>
 
-double complex z1 = I * I;
+double complex z1 = -1;
 
-const long double complex z2 = I * I;
+const long double complex z2 = -1;
 
-float complex z4 = 1+2.11*I;
+float complex z4 = 1;

             reply	other threads:[~2023-02-16 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 11:12 Alexandre Oliva [this message]
2023-02-22 14:49 Alexandre Oliva
2023-02-22 17:23 Alexandre Oliva
2023-02-23 13:48 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=20230216111245.C1B893858031@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).