public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jens Remus <jremus@linux.ibm.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Cc: Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [RFC PATCH 0/9] s390: Initial support to generate SFrame info from CFI directives in assembler
Date: Tue, 9 Apr 2024 16:19:57 +0200	[thread overview]
Message-ID: <669bfccf-aeb8-4719-967d-41784990a09a@linux.ibm.com> (raw)
In-Reply-To: <5a63d8b0-ae9f-4fb2-950d-4828d0b95f49@oracle.com>

Am 05.04.2024 um 20:26 schrieb Indu Bhagat:
> On 2/23/24 13:16, Indu Bhagat wrote:
>> On 2/23/24 09:07, Jens Remus wrote:
>>> This patch series adds initial support to the assembler on s390x to
>>> generate SFrame stack trace information from CFI directives. It is
>>> largely based on the respective AArch64 support.
>>>
>>> Please be aware that the SFrame support for s390x provided by patch 9
>>> of this series still has some open issues, which need to be addressed.
>>> Any ideas or assistance to overcome the current SFrame limitations
>>> listed below and in the patch description are very welcome.
>>>
>>> Patches 1-8 are generic cleanups and enhancements to the generation
>>> of SFrame information in the assembler. Patch 9 adds the initial s390x
>>> support and is purely RFC.
>>>
>>>
>>> Patches 1-3 are minor cleanups/enhancements to the existing SFrame
>>> support on AArch64 and x86 AMD64.
>>>
>>> Patch 4 enables readelf/objdump to dump the SFrame fixed offsets from
>>> CFA to the frame pointer (FP) and return address (RA).
>>>
>>> Patch 5 enhances an SFrame warning message to print the human readable
>>> DWARF call frame instruction name.
>>>
>>> Patch 6 and 7 resolve issues that cause the assembler to either generate
>>> bad SFrame FDE or to silently skip it. Both issues would be triggered by
>>> s390-specific SFrame error test cases introduced by patch 9.
>>>
>>> Patch 8 adds verbose assembler warning messages when generation of
>>> SFrame FDE is skipped.
>>>
>>
>> Thanks for fixing issues and enhancing SFrame handling in Binutils.
>>
> 
> Hi Jens,
> 
> I think it will be great to split this series and send a V2 for the 
> Patches 1-8 from your series. What do you think ?

Hi Indu,

thank you for your valuable feedback to my patch series! Sorry for the 
long delay in getting back to you.

That is an excellent suggestion to separate the non-s390 specific 
patches from the experimental s390 ones. I will do so shortly for both. 
Patches 1-8 have meanwhile grown to 1-15.

Regards,
Jens
-- 
Jens Remus
Linux on Z Development (D3303) and z/VSE Support
+49-7031-16-1128 Office
jremus@de.ibm.com

IBM

IBM Deutschland Research & Development GmbH; Vorsitzender des 
Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der 
Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/

  reply	other threads:[~2024-04-09 14:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 17:07 Jens Remus
2024-02-23 17:07 ` [PATCH v2 1/9] x86: Remove unused SFrame CFI RA register variable Jens Remus
2024-02-24  7:38   ` Indu Bhagat
2024-02-26 13:01     ` Jan Beulich
2024-02-26 14:51       ` Jens Remus
2024-02-27  9:08       ` Indu Bhagat
2024-02-27  9:11         ` Jan Beulich
2024-02-26 15:04     ` Jens Remus
2024-02-23 17:07 ` [PATCH v2 2/9] aarch64: Align SFrame terminology in comments to specs and x86 Jens Remus
2024-02-24  7:44   ` Indu Bhagat
2024-02-23 17:07 ` [PATCH v2 3/9] sframe: Enhance comments for SFRAME_CFA_*_REG macros Jens Remus
2024-02-24  7:46   ` Indu Bhagat
2024-02-26 13:51     ` Jan Beulich
2024-02-27  8:53       ` Indu Bhagat
2024-02-27  8:57         ` Jan Beulich
2024-02-27  9:01           ` Indu Bhagat
2024-02-23 17:07 ` [PATCH v2 4/9] readelf/objdump: Dump SFrame CFA fixed FP and RA offsets Jens Remus
2024-02-24  7:48   ` Indu Bhagat
2024-02-23 17:07 ` [PATCH v2 5/9] gas: Print DWARF call frame insn name in SFrame warning message Jens Remus
2024-02-24  7:56   ` Indu Bhagat
2024-02-26 15:37     ` Jens Remus
2024-02-23 17:07 ` [PATCH v2 6/9] gas: Skip SFrame FDE if CFI specifies non-FP/SP base register Jens Remus
2024-02-24  7:57   ` Indu Bhagat
2024-02-23 17:07 ` [PATCH v2 7/9] gas: Warn if SFrame FDE is skipped due to non-default return column Jens Remus
2024-02-24  8:43   ` Indu Bhagat
2024-02-26 16:19     ` Jens Remus
2024-02-23 17:07 ` [PATCH v2 8/9] gas: User readable warnings if SFrame FDE is not generated Jens Remus
2024-02-29  7:39   ` Indu Bhagat
2024-04-09 14:14     ` Jens Remus
2024-02-23 17:08 ` [RFC PATCH 9/9] s390: Initial support to generate .sframe from CFI directives in assembler Jens Remus
2024-02-29  7:01   ` Indu Bhagat
2024-04-09 15:07     ` Jens Remus
2024-02-23 17:27 ` [RFC PATCH 0/9] s390: Initial support to generate SFrame info " Jens Remus
2024-02-23 21:16 ` Indu Bhagat
2024-04-05 18:26   ` Indu Bhagat
2024-04-09 14:19     ` Jens Remus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-22 16:01 Jens Remus

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=669bfccf-aeb8-4719-967d-41784990a09a@linux.ibm.com \
    --to=jremus@linux.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --cc=krebbel@linux.ibm.com \
    /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).