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: Sun, 30 Jul 2023 19:50:14 +0000 [thread overview]
Message-ID: <bug-110419-4-m5kCkNPNZS@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 #17 from Mikael Morin <mikael at gcc dot gnu.org> ---
Created attachment 55660
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55660&action=edit
Update function type patch
This patch changes the dummy argument declaration type.
It changes the dump as follows.
--- m32/pr110419_comment4.f90.005t.original 2023-07-05 13:05:58.743843174
+0000
+++ pr110419_comment4.f90.005t.original 2023-07-30 19:31:20.880043687 +0000
@@ -1,5 +1,5 @@
__attribute__((fn spec (". r w ")))
-void val (character(kind=1)[1:1] & restrict x, character(kind=1)[1:1] c,
integer(kind=4) _x, integer(kind=4) _c)
+void val (character(kind=1)[1:1] & restrict x, character(kind=1) c,
integer(kind=4) _x, integer(kind=4) _c)
{
{
struct __st_parameter_dt dt_parm.0;
@@ -25,7 +25,7 @@
_gfortran_transfer_character_write (&dt_parm.1, &c, 1);
_gfortran_st_write_done (&dt_parm.1);
}
- if (c[1]{lb: 1 sz: 1} != (*x)[1]{lb: 1 sz: 1})
+ if ((*x)[1]{lb: 1 sz: 1} != c)
{
_gfortran_stop_numeric (1, 0);
}
@@ -36,7 +36,7 @@
__attribute__((fn spec (". ")))
void p ()
{
- static void val (character(kind=1)[1:1] & restrict, character(kind=1)[1:1],
integer(kind=4), integer(kind=4));
+ static void val (character(kind=1)[1:1] & restrict, character(kind=1),
integer(kind=4), integer(kind=4));
static integer(kind=4) a = 65;
{
It seems to fix comment #4 (both 32 and 64 bits).
next prev parent reply other threads:[~2023-07-30 19:50 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
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 [this message]
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-m5kCkNPNZS@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).