public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Edelsohn <dje@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-1700] aix: Debugging does not require a stack frame. Date: Mon, 12 Jun 2023 01:23:19 +0000 (GMT) [thread overview] Message-ID: <20230612012319.85D013858D28@sourceware.org> (raw) https://gcc.gnu.org/g:f47ecca87573244c138a585b2a734e4d7ab5d0a2 commit r14-1700-gf47ecca87573244c138a585b2a734e4d7ab5d0a2 Author: David Edelsohn <dje.gcc@gmail.com> Date: Sat Jun 3 20:27:16 2023 -0400 aix: Debugging does not require a stack frame. The rs6000 port has allocated a stack frame when debugging is enabled on AIX since the earliest versions of the port. Apparently the earliest versions of the debuggers for AIX had difficulty with stackless frames. Both AIX DBX and GDB support stackless frames on AIX, and IBM XLC, OpenXL and LLVM for AIX do not generate an extraneous stack frame when debugging is enabled. This patch updates the rs6000 stack info function to not set the stack frame flag when debugging is enabled for AIX. gcc/ChangeLog: * config/rs6000/rs6000-logue.cc (rs6000_stack_info): Do not require a stack frame when debugging is enabled for AIX. Signed-off-by: David Edelsohn <dje.gcc@gmail.com> Diff: --- gcc/config/rs6000/rs6000-logue.cc | 3 --- 1 file changed, 3 deletions(-) diff --git a/gcc/config/rs6000/rs6000-logue.cc b/gcc/config/rs6000/rs6000-logue.cc index bc6b153b59f..98846f781ec 100644 --- a/gcc/config/rs6000/rs6000-logue.cc +++ b/gcc/config/rs6000/rs6000-logue.cc @@ -928,9 +928,6 @@ rs6000_stack_info (void) else if (frame_pointer_needed) info->push_p = 1; - else if (TARGET_XCOFF && write_symbols != NO_DEBUG && !flag_compare_debug) - info->push_p = 1; - else info->push_p = non_fixed_size > (TARGET_32BIT ? 220 : 288);
reply other threads:[~2023-06-12 1:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230612012319.85D013858D28@sourceware.org \ --to=dje@gcc.gnu.org \ --cc=gcc-cvs@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).