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, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [PATCH] [testsuite] test for weak_undefined support and add options
Date: Sat, 18 Mar 2023 00:29:24 -0700	[thread overview]
Message-ID: <B2718468-5CB8-4BA7-AE0C-1A74DE92279E@comcast.net> (raw)
In-Reply-To: <orsfe59p2e.fsf@lxoliva.fsfla.org>

On Mar 15, 2023, at 11:40 PM, Alexandre Oliva <oliva@adacore.com> wrote:
> 
> On Mar 15, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> 
>> Regstrapped on ppc64-linux-gnu.  Also tested (with gcc-12) on multiple
>> *-vxworks7r2 targets (arm, aarch64, ppc64, x86, x86_64).  Ok to install?
> 
> Further testing revealed a problem in my attempted use of lappend in
> aapcs64.exp, in the previous version of the patch.  Fixed in this one,
> retested on aarch64-vxworks7r2.  Ok to install?

Ok.


  reply	other threads:[~2023-03-18  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  1:20 Alexandre Oliva
2023-03-16  6:40 ` Alexandre Oliva
2023-03-18  7:29   ` Mike Stump [this message]
2023-03-23  3:36     ` 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=B2718468-5CB8-4BA7-AE0C-1A74DE92279E@comcast.net \
    --to=mikestump@comcast.net \
    --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).