From: "stefansf at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug middle-end/108102] rust bootstrap comparison failure on s390x-linux-gnu
Date: Mon, 16 Jan 2023 09:46:46 +0000 [thread overview]
Message-ID: <bug-108102-35322-Y7NETb1R6Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108102-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108102
--- Comment #11 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> ---
Please find attached a reduced version of the initial problem. If compiled
with
g++ -O2 -march=arch13 -fno-exceptions (-g)
there is still a difference whether build with debug information or not:
diff <(objdump -d reduced.o-without-debug) <(objdump -d reduced.o-with-debug)
2c2
< reduced.o-without-debug: file format elf64-s390
---
> reduced.o-with-debug: file format elf64-s390
94,97c94,97
< 1b8: e5 48 f0 a8 00 00 mvghi 168(%r15),0
< 1be: e3 50 f0 c8 00 04 lg %r5,200(%r15)
< 1c4: 41 30 f0 a0 la %r3,160(%r15)
< 1c8: e3 50 f0 a0 00 24 stg %r5,160(%r15)
---
> 1b8: e3 50 f0 c8 00 04 lg %r5,200(%r15)
> 1be: e5 48 f0 a8 00 00 mvghi 168(%r15),0
> 1c4: e3 50 f0 a0 00 24 stg %r5,160(%r15)
> 1ca: 41 30 f0 a0 la %r3,160(%r15)
The corresponding insns are:
Without debug information:
mvghi => insn 207
lg => insn 206
la => insn 310
stg => insn 312
With debug information:
lg => insn 427
mvghi => insn 428
stg => insn 533
la => insn 531
In split3 the order of the insns are the same and change in sched2 where we
have:
Without debug information:
;; ======================================================
;; -- basic block 14 from 87 to 355 -- after reload
;; ======================================================
;; 0--> b 0: i 87 %r2=0 :nothing
;; 1--> b 0: i 88 {%r2=call
[`_ZN4Rust4TyTy9ParamType7resolveEv'];clobber %r14;}:nothing
;; 2--> b 0: i 207 [%r15+0xa8]=0 :nothing
;; 3--> b 0: i 206 %r5=[%r15+0xc8] :nothing
;; 4--> b 0: i 310 %r3=%r15+0xa0 :nothing
;; 5--> b 0: i 312 [%r15+0xa0]=%r5 :nothing
;; 6--> b 0: i 311 %r2=%r15+0xc0 :nothing
;; 7--> b 0: i 96 {call
[`_ZNSt6vectorIPN4Rust4TyTy8BaseTypeESaIS3_EE17_M_realloc_insertIN9__gnu_cxx17__normal_iteratorIPS3_S5_EEEEvT_'];clobber
%r14;}:nothing
;; 8--> b 0: i 355 pc=L174 :nothing
;; Ready list (final):
;; total time = 8
;; new head = 87
;; new tail = 355
With debug information:
;; ======================================================
;; -- basic block 14 from 201 to 585 -- after reload
;; ======================================================
;; 0--> b 0: i 201 debug_marker :nothing
;; 0--> b 0: i 202 %r2=0 :nothing
;; 1--> b 0: i 203 {%r2=call
[`_ZN4Rust4TyTy9ParamType7resolveEv'];clobber %r14;}:nothing
;; 1--> b 0: i 204 debug_marker :nothing
;; 1--> b 0: i 205 loc %r15+0xc0 :nothing
;; 1--> b 0: i 206 debug_marker :nothing
;; 1--> b 0: i 207 loc %r15+0xc0 :nothing
;; 1--> b 0: i 208 debug_marker :nothing
;; 1--> b 0: i 210 loc debug_implicit_ptr :nothing
;; 1--> b 0: i 211 loc [%r15+0xc8] :nothing
;; 1--> b 0: i 212 debug_marker :nothing
;; 1--> b 0: i 214 loc clobber :nothing
;; 1--> b 0: i 215 loc clobber :nothing
;; 1--> b 0: i 216 loc clobber :nothing
;; 2--> b 0: i 427 %r5=[%r15+0xc8] :nothing
;; 3--> b 0: i 428 [%r15+0xa8]=0 :nothing
;; 4--> b 0: i 533 [%r15+0xa0]=%r5 :nothing
;; 5--> b 0: i 531 %r3=%r15+0xa0 :nothing
;; 6--> b 0: i 532 %r2=%r15+0xc0 :nothing
;; 7--> b 0: i 222 {call
[`_ZNSt6vectorIPN4Rust4TyTy8BaseTypeESaIS3_EE17_M_realloc_insertIN9__gnu_cxx17__normal_iteratorIPS3_S5_EEEEvT_'];clobber
%r14;}:nothing
;; 7--> b 0: i 223 loc clobber :nothing
;; 8--> b 0: i 585 pc=L373 :nothing
;; Ready list (final):
;; total time = 8
;; new head = 201
;; new tail = 585
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-16 9:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 16:22 [Bug rust/108102] New: " doko at gcc dot gnu.org
2022-12-14 16:22 ` [Bug rust/108102] " doko at gcc dot gnu.org
2022-12-14 17:00 ` jakub at gcc dot gnu.org
2022-12-15 10:20 ` marxin at gcc dot gnu.org
2022-12-23 18:27 ` stefansf at linux dot ibm.com
2022-12-23 18:30 ` [Bug middle-end/108102] " pinskia at gcc dot gnu.org
2022-12-23 18:33 ` pinskia at gcc dot gnu.org
2022-12-23 20:58 ` stefansf at linux dot ibm.com
2022-12-23 21:06 ` pinskia at gcc dot gnu.org
2022-12-24 10:05 ` stefansf at linux dot ibm.com
2022-12-24 10:07 ` stefansf at linux dot ibm.com
2023-01-16 9:43 ` stefansf at linux dot ibm.com
2023-01-16 9:44 ` stefansf at linux dot ibm.com
2023-01-16 9:45 ` stefansf at linux dot ibm.com
2023-01-16 9:46 ` stefansf at linux dot ibm.com [this message]
2023-01-30 14:39 ` stefansf at linux dot ibm.com
2023-02-07 10:17 ` doko at gcc dot gnu.org
2023-02-07 10:28 ` stefansf at linux dot ibm.com
2023-02-13 14:33 ` cvs-commit at gcc dot gnu.org
2023-02-13 15:50 ` stefansf at linux dot ibm.com
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=bug-108102-35322-Y7NETb1R6Z@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
/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).