public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109478] FAIL: g++.dg/other/pr104989.C  -std=gnu++14 (internal compiler error: Segmentation fault)
Date: Fri, 21 Apr 2023 14:39:23 +0000	[thread overview]
Message-ID: <bug-109478-4-AGrafrhqQ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109478-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by John David Anglin
<danglin@gcc.gnu.org>:

https://gcc.gnu.org/g:dca9419cc3844d3cf3c06f51d5ca57e3b5f50920

commit r12-9461-gdca9419cc3844d3cf3c06f51d5ca57e3b5f50920
Author: John David Anglin <danglin@gcc.gnu.org>
Date:   Fri Apr 21 14:38:42 2023 +0000

    Fix handling of large arguments passed by value.

    2023-04-15  John David Anglin  <danglin@gcc.gnu.org>

    gcc/ChangeLog:

            PR target/109478
            * config/pa/pa-protos.h (pa_function_arg_size): Update prototype.
            * config/pa/pa.cc (pa_function_arg): Return NULL_RTX if argument
            size is zero.
            (pa_arg_partial_bytes): Don't call pa_function_arg_size twice.
            (pa_function_arg_size): Change return type to int.  Return zero
            for arguments larger than 1 GB.  Update comments.

      parent reply	other threads:[~2023-04-21 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 21:52 [Bug rtl-optimization/109478] New: " danglin at gcc dot gnu.org
2023-04-12 11:31 ` [Bug middle-end/109478] " rguenth at gcc dot gnu.org
2023-04-12 13:13 ` law at gcc dot gnu.org
2023-04-13 17:11 ` dave.anglin at bell dot net
2023-04-15 17:15 ` [Bug target/109478] " danglin at gcc dot gnu.org
2023-04-16  3:18 ` sjames at gcc dot gnu.org
2023-04-21 14:39 ` cvs-commit at gcc dot gnu.org [this message]

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-109478-4-AGrafrhqQ3@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).