public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/114133] problem passing a string pointer to a C function on solaris 32 bit and 64 bit
Date: Tue, 27 Feb 2024 16:11:08 +0000	[thread overview]
Message-ID: <bug-114133-4-TxdKrxjTfv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114133-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114133

--- Comment #3 from Gaius Mulley <gaius at gcc dot gnu.org> ---
At a guess the problem was the ZTyped constant (1 and 5).  Now the gimple IR
shows these constants as integers:

$ cat callingc10.mod.095i.comdats
PROC _M2_callingc10_init (INTEGER argc, PROC * argv, PROC * envp)
{
  INTEGER D.676;
  INTEGER D.675;
  INTEGER D.674;
  INTEGER _T35.0_1;
  PROC * _T36.1_2;
  INTEGER _T34.2_3;
  INTEGER _4;
  INTEGER _T37.3_5;
  INTEGER _T39.4_6;
  PROC * _T40.5_7;
  INTEGER _T38.6_8;
  INTEGER _9;
  INTEGER _T41.7_10;
  INTEGER _T43.8_11;
  PROC * _T44.9_12;
  INTEGER _T42.10_13;
  INTEGER _14;
  INTEGER _20;
  INTEGER _26;
  INTEGER _32;

  <bb 2> :
  _T34 = 1;
  _T35 = 5;
  _T36 = "hello";
  _T35.0_1 = _T35;
  _T36.1_2 = _T36;
  _T34.2_3 = _T34;
  _20 = funcptr (_T34.2_3, _T36.1_2, _T35.0_1);
  _4 = _20;
  _T37 = _4;
  _T37.3_5 = _T37;

  parent reply	other threads:[~2024-02-27 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 15:24 [Bug modula2/114133] New: " gaius at gcc dot gnu.org
2024-02-27 15:39 ` [Bug modula2/114133] " gaius at gcc dot gnu.org
2024-02-27 15:59 ` gaius at gcc dot gnu.org
2024-02-27 16:11 ` gaius at gcc dot gnu.org [this message]
2024-05-07 18:24 ` cvs-commit at gcc dot gnu.org
2024-05-07 18:57 ` cvs-commit at gcc dot gnu.org
2024-05-07 18:59 ` gaius 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-114133-4-TxdKrxjTfv@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).