public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, david.faust@oracle.com,
	"ro@cebitec.uni-bielefeld.de" <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [PATCH] Drop need for constant I in ctf test
Date: Fri, 17 Feb 2023 11:56:10 -0800	[thread overview]
Message-ID: <A89830E7-BA9A-4FAC-ABE1-8FE8D1A17010@comcast.net> (raw)
In-Reply-To: <or1qmou68k.fsf@lxoliva.fsfla.org>

On Feb 16, 2023, at 10:59 PM, Alexandre Oliva <oliva@adacore.com> wrote:
> 
> 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.
> 
> Regstrapped on x86_64-linux-gnu.
> Tested on arm-vxworks7 (gcc-12) and arm-eabi (trunk).  Ok to install?

Ok.


      reply	other threads:[~2023-02-17 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  6:59 Alexandre Oliva
2023-02-17 19:56 ` Mike Stump [this message]

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=A89830E7-BA9A-4FAC-ABE1-8FE8D1A17010@comcast.net \
    --to=mikestump@comcast.net \
    --cc=david.faust@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=oliva@adacore.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).