public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>,
	'Claudiu Zissulescu' <Claudiu.Zissulescu@synopsys.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [ARC PATCH] Use rlc r0, 0 to implement scc_ltu (i.e. carry_flag ? 1 : 0)
Date: Fri, 29 Sep 2023 16:02:00 -0600	[thread overview]
Message-ID: <b8003d66-7c1f-4eb2-9593-51c1118f3360@gmail.com> (raw)
In-Reply-To: <023301d9f319$7f90ac60$7eb20520$@nextmovesoftware.com>



On 9/29/23 15:11, Roger Sayle wrote:
> 
> Hi Claudiu,
>> The patch looks sane. Have you run dejagnu test suite?
> 
> I've not yet managed to set up an emulator or compile the entire toolchain,
> so my dejagnu results are only useful for catching (serious) problems in the
> compile only tests:
> 
>                  === gcc Summary ===
> 
> # of expected passes            91875
> # of unexpected failures        23768
> # of unexpected successes       23
> # of expected failures          1038
> # of unresolved testcases       19490
> # of unsupported tests          3819
> /home/roger/GCC/arc-linux/gcc/xgcc  version 14.0.0 20230828 (experimental)
> (GCC)
> 
> If someone could double check there are no issues on real hardware that
> would be great.  I'm not sure if ARC is one of the targets covered by Jeff
> Law's compile farm?
It is :-)  Runs daily, about 4:30 am UTC.  So if the bits go in we'd 
have data within 24hrs.


Jeff


  reply	other threads:[~2023-09-29 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 15:54 [ARC PATCH] Use rlc r0,0 " Roger Sayle
2023-09-29 18:04 ` Claudiu Zissulescu
2023-09-29 21:11   ` Roger Sayle
2023-09-29 22:02     ` Jeff Law [this message]
2023-10-01 14:32       ` [ARC PATCH] Use rlc r0, 0 " Claudiu Zissulescu
2023-10-02 16:39         ` Claudiu Zissulescu

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=b8003d66-7c1f-4eb2-9593-51c1118f3360@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=roger@nextmovesoftware.com \
    /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).