public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf 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, 29 Jun 2023 17:39:26 +0000	[thread overview]
Message-ID: <bug-110419-4-Yv78xTMU2e@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 #4 from anlauf at gcc dot gnu.org ---
It appears that the issue could be studied with the following code:

program p
  implicit none
  integer :: a = 65
  call val ("A", char(a))
contains
  subroutine val (x, c)
    character(kind=1), intent(in) :: x  ! control: pass by reference
    character(kind=1), value      :: c
    print *, "by reference(kind=1): ", x
    print *, "by value    (kind=1): ", c
    if (c /= x)   stop 1
  end
end

If this works on LE with -m64 and -m32, and also on BE with -m64,
why would it fail on BE with -m32 ?

  parent reply	other threads:[~2023-06-29 17: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 [this message]
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
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-Yv78xTMU2e@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).