public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/104274] FAIL: gcc.dg/analyzer/pr97029.c (test for excess errors) Date: Thu, 10 Feb 2022 23:38:58 +0000 [thread overview] Message-ID: <bug-104274-4-rcuzrvXRMp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104274-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104274 --- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> --- In gimplify_parameters: x86_64: (gdb) p data.arg $2 = {type = <record_type 0x7fffea77cbd0 vj>, mode = E_BLKmode, named = 1, pass_by_reference = 0} hppa64-hpux11.3: (gdb) p data.arg $29 = {type = <pointer_type 0x7fffea73bbd0>, mode = E_DImode, named = 1, pass_by_reference = 1} so this seems to only be happening for empty structs, when passing them by reference. Specifically, for both targets we reach: VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV Breakpoint 12, pass_by_reference (ca=0x7fffffffd860, arg=...) at ../../src/gcc/calls.cc:921 921 return targetm.calls.pass_by_reference (pack_cumulative_args (ca), arg); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ and on pa, size == 0, so we pass by reference: 6367 static bool 6368 pa_pass_by_reference (cumulative_args_t, const function_arg_info &arg) 6369 { 6370 HOST_WIDE_INT size = arg.type_size_in_bytes (); 6371 if (TARGET_64BIT) 6372 return size <= 0; 6373 else 6374 return size <= 0 || size > 8; 6375 } whereas on x86_64, ix86_pass_by_reference returns false.
next prev parent reply other threads:[~2022-02-10 23:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-28 18:57 [Bug analyzer/104274] New: " danglin at gcc dot gnu.org 2022-02-10 23:02 ` [Bug analyzer/104274] " dmalcolm at gcc dot gnu.org 2022-02-10 23:38 ` dmalcolm at gcc dot gnu.org [this message] 2022-02-10 23:50 ` dmalcolm at gcc dot gnu.org 2022-02-10 23:59 ` dmalcolm at gcc dot gnu.org 2022-02-11 13:47 ` cvs-commit at gcc dot gnu.org 2022-02-11 13:53 ` dmalcolm 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-104274-4-rcuzrvXRMp@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).