public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org, Rene Rebe <rene@exactcode.de>
Subject: Re: [PATCH 2/3] Enabled LRA for ia64.
Date: Wed, 12 Jun 2024 19:54:06 +0100	[thread overview]
Message-ID: <Zmnuzmz4PrAIdKBS@zen.kayari.org> (raw)
In-Reply-To: <98ac79fc-6c97-4028-b43b-abbcfcd36adc@web.de>

On 12/06/24 16:09 +0200, Frank Scheiner wrote:
>Dear Richard,
>
>On 12.06.24 13:01, Richard Biener wrote:
>>[...]
>>I can find two gcc-testresult postings, one appearantly with LRA
>>and one without?  Both from May:
>>
>>https://sourceware.org/pipermail/gcc-testresults/2024-May/816422.html
>>https://sourceware.org/pipermail/gcc-testresults/2024-May/816346.html
>>
>>somehow for example libstdc++ summaries were not merged, it might
>>be you do not have recent python installed on the system?  Or you
>>didn't use contrib/test_summary to create those mails.
>
>No, I did not use contrib/test_summary. But I still have tarballs of
>both testsuite runs, so could still produce these summaries - I hope?

It looks like the results at
https://gcc.gnu.org/pipermail/gcc-testresults/2024-May/816422.html are
just what's printed on standard out, including output from 'make -j4'
so not combined into one set of results.

It would certainly be better to either get the results from the .sum
files, or just use the contrib/test_summary script to do that for you.

>Do I need to run this on the host that did the testing or can I run it
>on my NFS server where the tarballs are actually located, too?

I don't think the script cares where it's run, it just looks at text
files which should work on any host.

>Architectures are different though, the NFS server is 32-bit ARM.

Text is text.


  reply	other threads:[~2024-06-12 18:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45833A6D-A84C-4276-AADB-BE2923886F64@exactcode.de>
     [not found] ` <A935D68A-1B29-421A-A239-52CA50ADA239@suse.de>
     [not found]   ` <3DAB006A-ACE2-4BEC-AA01-87625DBEE259@exactcode.de>
2024-06-12 10:33     ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Rene Rebe
2024-06-12 10:42       ` [PATCH 1/3] " Rene Rebe
2024-06-12 18:40         ` Jonathan Wakely
2024-06-12 18:48           ` Jonathan Wakely
2024-06-13  8:58         ` Gerald Pfeifer
2024-06-12 10:42       ` [PATCH 2/3] Enabled LRA for ia64 Rene Rebe
2024-06-12 11:01         ` Richard Biener
2024-06-12 12:50           ` René Rebe
2024-06-12 13:00             ` Richard Biener
2024-06-12 13:19               ` René Rebe
2024-06-12 14:03                 ` Frank Scheiner
2024-06-12 14:09           ` Frank Scheiner
2024-06-12 18:54             ` Jonathan Wakely [this message]
2024-06-12 20:59               ` Frank Scheiner
2024-06-13 10:33                 ` Jonathan Wakely
2024-06-13 14:11                   ` Jeff Law
2024-06-13 14:16                     ` Jonathan Wakely
2024-06-13 14:18                       ` Jonathan Wakely
2024-06-14 11:07                   ` Frank Scheiner
2024-06-14 12:53                     ` Jonathan Wakely
2024-06-14 13:07                       ` Frank Scheiner
2024-06-14 13:23                         ` Jonathan Wakely
2024-06-17 18:03                           ` Joseph Myers
2024-06-17 18:53                             ` Jonathan Wakely
2024-06-17 19:36                               ` Frank Scheiner
2024-06-13  7:02             ` Richard Biener
2024-06-12 10:43       ` [PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer Rene Rebe
2024-06-12 19:03         ` Jonathan Wakely
2024-06-12 18:44       ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Jonathan Wakely

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=Zmnuzmz4PrAIdKBS@zen.kayari.org \
    --to=jwakely@redhat.com \
    --cc=frank.scheiner@web.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rene@exactcode.de \
    --cc=rguenther@suse.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).