public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pkubaj at anongoth dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/89494] Bootstrap error when using GCC 4.2.1 Date: Sun, 12 Apr 2020 15:54:12 +0000 [thread overview] Message-ID: <bug-89494-4-IS12i4pG49@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89494-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89494 --- Comment #16 from Piotr Kubaj <pkubaj at anongoth dot pl> --- 634afa05a8cbff010480088811fe1f39eca70c1d is the first bad commit commit 634afa05a8cbff010480088811fe1f39eca70c1d Author: Richard Sandiford <richard.sandiford@arm.com> Date: Tue Aug 20 08:53:52 2019 +0000 Make function.c use function_arg_info internally This patch adds a function_arg_info field to assign_parm_data_one, so that: - passed_type -> arg.type - promoted_mode -> arg.mode - named_arg -> arg.named We can then pass this function_arg_info directly to the converted hooks. Between the initialisation of the assign_parm_data_one and the application of promotion rules (which is a state internal to assign_parm_find_data_types), arg.mode is equivalent to passed_mode (i.e. to TYPE_MODE). 2019-08-20 Richard Sandiford <richard.sandiford@arm.com> gcc/ * function.c (assign_parm_data_one): Replace passed_type, promoted_mode and named_arg with a function_arg_info field. (assign_parm_find_data_types): Remove local variables and assign directly to "data". Make data->passed_mode shadow data->arg.mode until promotion, then assign the promoted mode to data->arg.mode. (assign_parms_setup_varargs, assign_parm_find_entry_rtl) (assign_parm_find_stack_rtl, assign_parm_adjust_entry_rtl) (assign_parm_remove_parallels, assign_parm_setup_block_p) (assign_parm_setup_block, assign_parm_setup_reg) (assign_parm_setup_stack, assign_parms, gimplify_parameters): Use arg.mode instead of promoted_mode, arg.type instead of passed_type and arg.named instead of named_arg. Use data->arg for function_arg_info structures that had the field values passed_type, promoted_mode and named_arg. Base other function_arg_infos on data->arg, changing the necessary properties. From-SVN: r274705 gcc/ChangeLog | 19 +++++++ gcc/function.c | 168 +++++++++++++++++++++++++-------------------------------- 2 files changed, 92 insertions(+), 95 deletions(-)
next prev parent reply other threads:[~2020-04-12 15:54 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89494-4@http.gcc.gnu.org/bugzilla/> 2020-04-11 3:15 ` pkubaj at anongoth dot pl 2020-04-11 18:02 ` pkubaj at anongoth dot pl 2020-04-11 18:08 ` pkubaj at anongoth dot pl 2020-04-12 11:18 ` pkubaj at anongoth dot pl 2020-04-12 15:54 ` pkubaj at anongoth dot pl [this message] 2020-04-14 20:36 ` jakub at gcc dot gnu.org 2020-04-14 21:08 ` iains at gcc dot gnu.org 2020-04-14 21:13 ` jakub at gcc dot gnu.org 2020-04-15 12:20 ` jakub at gcc dot gnu.org 2020-04-15 13:17 ` cvs-commit at gcc dot gnu.org 2020-04-15 13:42 ` pkubaj at anongoth dot pl 2020-04-15 14:46 ` jakub at gcc dot gnu.org 2020-04-16 8:16 ` cvs-commit at gcc dot gnu.org 2020-05-01 1:36 ` pkubaj at anongoth dot pl 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2021-03-24 20:03 ` iains at gcc dot gnu.org 2021-03-24 20:55 ` pkubaj at anongoth dot pl 2021-03-24 21:12 ` iains at gcc dot gnu.org 2021-04-10 17:03 ` pkubaj at anongoth dot pl 2024-03-17 4:18 ` iains at gcc dot gnu.org 2024-03-17 10:45 ` pkubaj at anongoth dot pl 2024-03-17 19:00 ` pinskia 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-89494-4-IS12i4pG49@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).