public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aagarwa at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100799] Stackoverflow in optimized code on PPC Date: Fri, 22 Mar 2024 07:44:34 +0000 [thread overview] Message-ID: <bug-100799-4-bDRWaZneSD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100799-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799 --- Comment #33 from Ajit Kumar Agarwal <aagarwa at gcc dot gnu.org> --- Sent the patch for review. Here is the patch: PATCH] rs6000: Stackoverflow in optimized code on PPC (PR100799) When using FlexiBLAS with OpenBLAS we noticed corruption of the parameters passed to OpenBLAS functions. FlexiBLAS basically provides a BLAS interface where each function is a stub that forwards the arguments to a real BLAS lib, like OpenBLAS. Fixes the corruption of caller frame checking number of arguments is less than equal to GP_ARG_NUM_REG (8) excluding hidden unused DECLS. 2024-03-22 Ajit Kumar Agarwal <aagarwa1@linux.ibm.com> gcc/ChangeLog: PR rtk-optimization/100799 * config/rs600/rs600-calls.cc (rs6000_function_arg): Don't generate parameter save area if number of arguments passed less than equal to GP_ARG_NUM_REG (8) excluding hidden paramter. * function.cc (assign_parms_initialize_all): Check for hidden parameter in fortran code and set the flag hidden_string_length and actual paramter passed excluding hidden unused DECLS. * function.h: Add new field hidden_string_length and actual_parm_length in function structure.
next prev parent reply other threads:[~2024-03-22 7:44 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 11:20 [Bug fortran/100799] New: " alexander.grund@tu-dresden.de 2021-05-28 16:42 ` [Bug target/100799] " alexander.grund@tu-dresden.de 2021-06-01 19:08 ` bergner at gcc dot gnu.org 2021-06-01 21:09 ` segher at gcc dot gnu.org 2021-06-02 0:31 ` amodra at gmail dot com 2021-10-05 22:45 ` bergner at gcc dot gnu.org 2022-01-09 11:13 ` kenneth.hoste at ugent dot be 2022-07-08 10:53 ` alexander.grund@tu-dresden.de 2022-07-08 16:38 ` bergner at gcc dot gnu.org 2022-07-14 20:10 ` bergner at gcc dot gnu.org 2022-07-20 11:45 ` alexander.grund@tu-dresden.de 2022-07-20 14:14 ` alexander.grund@tu-dresden.de 2022-07-20 17:42 ` segher at gcc dot gnu.org 2022-07-20 17:59 ` segher at gcc dot gnu.org 2022-09-13 19:29 ` segher at gcc dot gnu.org 2022-09-19 5:46 ` jskumari at gcc dot gnu.org 2022-09-20 22:45 ` segher at gcc dot gnu.org 2022-10-17 8:17 ` jskumari at gcc dot gnu.org 2022-10-17 9:42 ` jskumari at gcc dot gnu.org 2022-10-17 17:10 ` jskumari at gcc dot gnu.org 2022-10-31 3:00 ` linkw at gcc dot gnu.org 2022-11-09 16:43 ` jskumari at gcc dot gnu.org 2023-06-19 20:25 ` bergner at gcc dot gnu.org 2024-02-21 7:38 ` jakub at gcc dot gnu.org 2024-02-22 2:51 ` bergner at gcc dot gnu.org 2024-02-22 14:44 ` bergner at gcc dot gnu.org 2024-02-22 14:59 ` jakub at gcc dot gnu.org 2024-02-25 0:39 ` bergner at gcc dot gnu.org 2024-02-26 9:58 ` jakub at gcc dot gnu.org 2024-02-27 0:45 ` bergner at gcc dot gnu.org 2024-02-27 7:26 ` jakub at gcc dot gnu.org 2024-02-27 15:30 ` bergner at gcc dot gnu.org 2024-03-01 15:25 ` bergner at gcc dot gnu.org 2024-03-22 7:44 ` aagarwa at gcc dot gnu.org [this message] 2024-03-22 7:45 ` aagarwa 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-100799-4-bDRWaZneSD@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).