From: Frank Scheiner <frank.scheiner@web.de>
To: Jonathan Wakely <jwakely@redhat.com>, Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Rene Rebe <rene@exactcode.de>
Subject: Re: [PATCH 2/3] Enabled LRA for ia64.
Date: Wed, 12 Jun 2024 22:59:51 +0200 [thread overview]
Message-ID: <b52e5d8a-14e4-455f-82fd-a8488faa44e6@web.de> (raw)
In-Reply-To: <Zmnuzmz4PrAIdKBS@zen.kayari.org>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Hi Jonathan, Richard,
On 12.06.24 20:54, Jonathan Wakely wrote:
> 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.
That's what it is, yes.
> 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.
Ok, I posted the results as created by contrib/test_summary now:
1. non-LRA version on [1]
2. LRA version on [2]
[1]: https://gcc.gnu.org/pipermail/gcc-testresults/2024-June/817267.html
[2]: https://gcc.gnu.org/pipermail/gcc-testresults/2024-June/817268.html
The difference 2 compared to 1 is attached.
>> 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.
It looks like it worked fine. :-)
Cheers,
Frank
[-- Attachment #2: gcc-15-lra-to-non-lra-testsute-summary.diff --]
[-- Type: text/x-patch, Size: 6196 bytes --]
diff --git a/gcc-15-testsuite-summary.log b/gcc-15-lra-testsuite-summary.log
index b7acc04..558079a 100644
--- a/gcc-15-testsuite-summary.log
+++ b/gcc-15-lra-testsuite-summary.log
@@ -306,13 +306,12 @@ FAIL: gcc.dg/guality/csttest.c -Og -DPREVENT_OPTIMIZATION line 55 q == -(0x1ef
FAIL: gcc.dg/guality/csttest.c -Og -DPREVENT_OPTIMIZATION line 55 r == -(0x1efULL << 50)
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/guality.c -O0 execution test
-XPASS: gcc.dg/guality/guality.c -O3 -g -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params-2.c -O1 -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params-2.c -O2 -DPREVENT_OPTIMIZATION execution test
+FAIL: gcc.dg/guality/inline-params-2.c -O3 -g -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params-2.c -Os -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params-2.c -Og -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params.c -O1 -DPREVENT_OPTIMIZATION execution test
-XPASS: gcc.dg/guality/inline-params.c -O3 -g -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/inline-params.c -Og -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/ipa-sra-1.c -O1 -DPREVENT_OPTIMIZATION line 19 k == 3
FAIL: gcc.dg/guality/ipa-sra-1.c -O1 -DPREVENT_OPTIMIZATION line 31 k == 3
@@ -434,6 +433,7 @@ FAIL: gcc.dg/guality/pr41447-1.c -Os -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/pr41447-1.c -Og -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/pr41616-1.c -O1 -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/pr41616-1.c -O2 -DPREVENT_OPTIMIZATION execution test
+FAIL: gcc.dg/guality/pr41616-1.c -O3 -g -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/pr41616-1.c -Og -DPREVENT_OPTIMIZATION execution test
FAIL: gcc.dg/guality/pr43051-1.c -Os -DPREVENT_OPTIMIZATION line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43077-1.c -O0 line 19 vara == 1
@@ -798,10 +798,10 @@ FAIL: gcc.dg/tree-prof/crossmodule-indircall-1a.c compilation, -fprofile-genera
UNRESOLVED: gcc.dg/tree-prof/crossmodule-indircall-1a.c compilation, -fprofile-use -D_PROFILE_USE
UNRESOLVED: gcc.dg/tree-prof/crossmodule-indircall-1a.c execution, -fprofile-generate -D_PROFILE_GENERATE
UNRESOLVED: gcc.dg/tree-prof/crossmodule-indircall-1a.c execution, -fprofile-use -D_PROFILE_USE
-FAIL: gcc.dg/tree-prof/pr77698.c compilation, -fprofile-generate -D_PROFILE_GENERATE
-UNRESOLVED: gcc.dg/tree-prof/pr77698.c compilation, -fprofile-use -D_PROFILE_USE
-UNRESOLVED: gcc.dg/tree-prof/pr77698.c execution, -fprofile-generate -D_PROFILE_GENERATE
-UNRESOLVED: gcc.dg/tree-prof/pr77698.c execution, -fprofile-use -D_PROFILE_USE
+FAIL: gcc.dg/tree-prof/pr47187.c compilation, -fprofile-generate -D_PROFILE_GENERATE
+UNRESOLVED: gcc.dg/tree-prof/pr47187.c compilation, -fprofile-use -D_PROFILE_USE
+UNRESOLVED: gcc.dg/tree-prof/pr47187.c execution, -fprofile-generate -D_PROFILE_GENERATE
+UNRESOLVED: gcc.dg/tree-prof/pr47187.c execution, -fprofile-use -D_PROFILE_USE
FAIL: gcc.dg/tree-ssa/abs-4.c scan-tree-dump-times optimized "= -" 3
FAIL: gcc.dg/tree-ssa/abs-4.c scan-tree-dump-times optimized "= ABS_EXPR" 3
FAIL: gcc.dg/tree-ssa/asm-2.c (test for excess errors)
@@ -953,18 +953,21 @@ FAIL: gcc.target/ia64/pr49303.c (test for excess errors)
=== gcc Summary ===
-# of expected passes 134719
-# of unexpected failures 899
-# of unexpected successes 21
-# of expected failures 1362
+# of expected passes 134769
+# of unexpected failures 901
+# of unexpected successes 19
+# of expected failures 1364
# of unresolved testcases 23
-# of unsupported tests 3081
-/dev/shm/gcc-15/src.gcc.ia64-toolchain-3.240529.112623.549077/gcc/gcc.build.lnx/gcc/xgcc version 15.0.0 20240528 (experimental) (GCC)
+# of unsupported tests 3036
+/dev/shm/gcc-15-lra/src.gcc.ia64-toolchain-3.240529.123346.921189/gcc/gcc.build.lnx/gcc/xgcc version 15.0.0 20240528 (experimental) (GCC)
=== gfortran tests ===
Running target unix
+FAIL: gfortran.dg/default_initialization_3.f90 -O3 -g (internal compiler error: in create_block_for_bookkeeping, at sel-sched.cc:4557)
+FAIL: gfortran.dg/default_initialization_3.f90 -O3 -g (test for excess errors)
+UNRESOLVED: gfortran.dg/default_initialization_3.f90 -O3 -g compilation failed to produce executable
FAIL: gfortran.dg/pr95690.f90 -O (test for errors, line 6)
FAIL: gfortran.dg/pr95690.f90 -O (test for excess errors)
FAIL: gfortran.dg/guality/arg1.f90 -O1 line 14 a(10) == 10
@@ -978,11 +981,12 @@ FAIL: gfortran.dg/vect/vect-2.f90 -O scan-tree-dump-times vect "Alignment of
=== gfortran Summary ===
-# of expected passes 69618
-# of unexpected failures 10
+# of expected passes 69616
+# of unexpected failures 12
# of expected failures 273
+# of unresolved testcases 1
# of unsupported tests 168
-/dev/shm/gcc-15/src.gcc.ia64-toolchain-3.240529.112623.549077/gcc/gcc.build.lnx/gcc/gfortran version 15.0.0 20240528 (experimental) (GCC)
+/dev/shm/gcc-15-lra/src.gcc.ia64-toolchain-3.240529.123346.921189/gcc/gcc.build.lnx/gcc/gfortran version 15.0.0 20240528 (experimental) (GCC)
=== g++ tests ===
@@ -1201,7 +1205,7 @@ FAIL: g++.dg/tree-prof/pr35545.C scan-tree-dump-not optimized "OBJ_TYPE_REF"
# of expected failures 2595
# of unresolved testcases 5
# of unsupported tests 11542
-/dev/shm/gcc-15/src.gcc.ia64-toolchain-3.240529.112623.549077/gcc/gcc.build.lnx/gcc/xg++ version 15.0.0 20240528 (experimental) (GCC)
+/dev/shm/gcc-15-lra/src.gcc.ia64-toolchain-3.240529.123346.921189/gcc/gcc.build.lnx/gcc/xg++ version 15.0.0 20240528 (experimental) (GCC)
=== objc tests ===
@@ -1212,7 +1216,7 @@ Running target unix
# of expected passes 2778
# of unsupported tests 58
-/dev/shm/gcc-15/src.gcc.ia64-toolchain-3.240529.112623.549077/gcc/gcc.build.lnx/gcc/xgcc version 15.0.0 20240528 (experimental) (GCC)
+/dev/shm/gcc-15-lra/src.gcc.ia64-toolchain-3.240529.123346.921189/gcc/gcc.build.lnx/gcc/xgcc version 15.0.0 20240528 (experimental) (GCC)
=== libatomic tests ===
next prev parent reply other threads:[~2024-06-12 21:00 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
2024-06-12 20:59 ` Frank Scheiner [this message]
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=b52e5d8a-14e4-455f-82fd-a8488faa44e6@web.de \
--to=frank.scheiner@web.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--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).