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/112334] ICE in gen_untyped_return arm.md:9197 while compiling harden-cfr-bret.c
Date: Tue, 12 Dec 2023 04:16:11 +0000	[thread overview]
Message-ID: <bug-112334-4-AQk9j4HDSr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112334-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

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

commit r14-6446-gd96533559e26dd0c86f0708fa46eef65c35f7b90
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue Dec 12 01:12:04 2023 -0300

    untyped calls: enable target switching [PR112334]

    The computation of apply_args_size and apply_result_size is saved in a
    static variable, so that the corresponding _mode arrays are
    initialized only once.  That is not compatible with switchable
    targets, and ARM's arm_set_current_function, by saving and restoring
    target globals, exercises this problem with a testcase such as that in
    the PR, in which more than one function in the translation unit calls
    __builtin_apply or __builtin_return, respectively.

    This patch moves the _size statics into the target_builtins array,
    with a bit of ugliness over _plus_one so that zero initialization of
    the struct does the right thing.


    for  gcc/ChangeLog

            PR target/112334
            * builtins.h (target_builtins): Add fields for apply_args_size
            and apply_result_size.
            * builtins.cc (apply_args_size, apply_result_size): Cache
            results in fields rather than in static variables.
            (get_apply_args_size, set_apply_args_size): New.
            (get_apply_result_size, set_apply_result_size): New.

  parent reply	other threads:[~2023-12-12  4:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 13:18 [Bug target/112334] New: " fkastl at suse dot cz
2023-11-02 13:03 ` [Bug target/112334] " rearnsha at gcc dot gnu.org
2023-12-01 17:38 ` cvs-commit at gcc dot gnu.org
2023-12-06 21:47 ` aoliva at gcc dot gnu.org
2023-12-12  4:16 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-12  4:46 ` aoliva 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-112334-4-AQk9j4HDSr@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).