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 d/110712] d: ICE: verify_gimple_failed (conversion of register to a different size in 'view_convert_expr')
Date: Sun, 29 Oct 2023 19:23:48 +0000	[thread overview]
Message-ID: <bug-110712-4-cGqkduokRS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110712-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:77f7d469e923f2bb1d21d3875290ce738262d42b

commit r12-9951-g77f7d469e923f2bb1d21d3875290ce738262d42b
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Sun Oct 29 20:13:14 2023 +0100

    d: Fix ICE: verify_gimple_failed (conversion of register to a different
size in 'view_convert_expr')

    Static arrays in D are passed around by value, rather than decaying to a
    pointer.  On x86_64 __builtin_va_list is an exception to this rule, but
    semantically it's still treated as a static array.

    This makes certain assignment operations fail due a mismatch in types.
    As all examples in the test program are rejected by C/C++ front-ends,
    these are now errors in D too to be consistent.

            PR d/110712

    gcc/d/ChangeLog:

            * d-codegen.cc (d_build_call): Update call to convert_for_argument.
            * d-convert.cc (is_valist_parameter_type): New function.
            (check_valist_conversion): New function.
            (convert_for_assignment): Update signature.  Add check whether
            assigning va_list is permissible.
            (convert_for_argument): Likewise.
            * d-tree.h (convert_for_assignment): Update signature.
            (convert_for_argument): Likewise.
            * expr.cc (ExprVisitor::visit (AssignExp *)): Update call to
            convert_for_assignment.

    gcc/testsuite/ChangeLog:

            * gdc.dg/pr110712.d: New test.

    (cherry picked from commit ea8ffdcadb388b531adf4772287e7987a82a84b7)

  parent reply	other threads:[~2023-10-29 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 10:37 [Bug d/110712] New: " ibuclaw at gdcproject dot org
2023-07-18 11:55 ` [Bug d/110712] " rguenth at gcc dot gnu.org
2023-07-19 15:16 ` ibuclaw at gdcproject dot org
2023-07-19 15:24 ` ibuclaw at gdcproject dot org
2023-10-29 19:21 ` cvs-commit at gcc dot gnu.org
2023-10-29 19:23 ` cvs-commit at gcc dot gnu.org
2023-10-29 19:23 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-29 19:25 ` ibuclaw 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-110712-4-cGqkduokRS@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).