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 15:39:12 +0000 [thread overview] Message-ID: <bug-114133-4-3kE12rGzyw@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 Gaius Mulley <gaius at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Last reconfirmed| |2024-02-27 --- Comment #1 from Gaius Mulley <gaius at gcc dot gnu.org> --- The gimple IR looks correct, given the input code: MODULE callingc10 ; FROM cvararg IMPORT funcptr ; FROM SYSTEM IMPORT ADR ; BEGIN IF funcptr (1, "hello", 5) = 1 THEN END ; IF funcptr (1, "hello" + " ", 6) = 1 THEN END ; IF funcptr (1, "hello" + " " + "world", 11) = 1 THEN END END callingc10. $ gm2 -g callingc10.mod -c -fdump-ipa-all $ cat callingc10.mod.095i.comdats ... PROC _M2_callingc10_init (INTEGER argc, PROC * argv, PROC * envp) { INTEGER D.670; INTEGER D.669; INTEGER D.668; PROC * _T34.0_1; INTEGER _2; INTEGER _T35.1_3; PROC * _T36.2_4; INTEGER _5; INTEGER _T37.3_6; PROC * _T38.4_7; INTEGER _8; INTEGER _12; INTEGER _16; INTEGER _20; <bb 2> : _T34 = "hello"; _T34.0_1 = _T34; _12 = funcptr (1, _T34.0_1, 5); _2 = _12; _T35 = _2; _T35.1_3 = _T35; ...
next prev parent reply other threads:[~2024-02-27 15:39 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 ` gaius at gcc dot gnu.org [this message] 2024-02-27 15:59 ` [Bug modula2/114133] " gaius at gcc dot gnu.org 2024-02-27 16:11 ` gaius at gcc dot gnu.org 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-3kE12rGzyw@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: linkBe 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).