public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/110419] [14 regression] new test case gfortran.dg/value_9.f90 in r14-2050-gd130ae8499e0c6 fails
Date: Thu, 06 Jul 2023 08:38:51 +0000 [thread overview]
Message-ID: <bug-110419-4-RovnKm8jLl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110419-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110419
--- Comment #14 from Mikael Morin <mikael at gcc dot gnu.org> ---
The tree optimized dumps are almost the same for 32 and 64 bits.
The expand dumps show more significant differences.
The 64 bits dump shows the register r4 is saved to memory with:
(insn 3 2 4 2 (set (mem/c:QI (plus:DI (reg/f:DI 111 virtual-incoming-args)
(const_int 8 [0x8])) [10 c+0 S1 A64])
(reg:QI 4 4 [ c ])) "pr110419_comment4.f90":6:16 -1
(nil))
The 32 bits dump shows:
(insn 3 2 4 2 (set (reg/v:SI 119)
(reg:SI 4 4)) "pr110419_comment4.f90":6:16 -1
(nil))
(insn 4 3 5 2 (set (reg:QI 120)
(mem/c:QI (reg/v:SI 119) [10 c+0 S1 A8])) "pr110419_comment4.f90":6:16
-1
(nil))
next prev parent reply other threads:[~2023-07-06 8:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 21:28 [Bug other/110419] New: " seurer at gcc dot gnu.org
2023-06-27 8:52 ` [Bug testsuite/110419] " rguenth at gcc dot gnu.org
2023-06-29 7:04 ` mikael at gcc dot gnu.org
2023-06-29 7:12 ` mikael at gcc dot gnu.org
2023-06-29 15:41 ` seurer at gcc dot gnu.org
2023-06-29 17:39 ` anlauf at gcc dot gnu.org
2023-07-02 19:19 ` anlauf at gcc dot gnu.org
2023-07-05 13:31 ` mikael at gcc dot gnu.org
2023-07-05 13:45 ` mikael at gcc dot gnu.org
2023-07-05 13:46 ` mikael at gcc dot gnu.org
2023-07-05 13:47 ` mikael at gcc dot gnu.org
2023-07-05 13:54 ` mikael at gcc dot gnu.org
2023-07-06 8:32 ` mikael at gcc dot gnu.org
2023-07-06 8:33 ` mikael at gcc dot gnu.org
2023-07-06 8:34 ` mikael at gcc dot gnu.org
2023-07-06 8:38 ` mikael at gcc dot gnu.org [this message]
2023-07-15 10:35 ` mikael at gcc dot gnu.org
2023-07-18 20:09 ` dje at gcc dot gnu.org
2023-07-30 19:50 ` mikael at gcc dot gnu.org
2023-07-31 14:58 ` mikael at gcc dot gnu.org
2023-08-10 7:40 ` mikael at gcc dot gnu.org
2023-08-14 20:11 ` cvs-commit at gcc dot gnu.org
2023-08-15 9:17 ` mikael at gcc dot gnu.org
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-110419-4-RovnKm8jLl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).