https://sourceware.org/bugzilla/show_bug.cgi?id=33175
--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The binutils-2_45-branch branch has been updated by Nick Clifton <ni...@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3fd0711530db4c414cb230837fc72a400dd312d4 commit 3fd0711530db4c414cb230837fc72a400dd312d4 Author: Indu Bhagat <indu.bha...@oracle.com> Date: Sun Jul 27 09:11:44 2025 +0100 [PATCH] gas: sframe: command line option takes precedence over gas directive to emit .sframe section. Fix PR gas/33175 sframe: --gsframe=no does not disable when .cfi_sections directive with .sframe --gsframe=no should also disable generation of SFrame section when explicit CFI directive: .cfi_sections .sframe is specified in the input. This means we need to track whether SFrame generation was explicitly disabled by the user. Introduce a new enum to facilitate disambiguation between GEN_SFRAME_DEFAULT_NONE and GEN_SFRAME_DISABLED. While fixing the bug by adding the enum, keep the upcoming requirement in mind: we will also need to disambiguate between --enable-default-sframe and user-specified --gsframe/--gsframe=yes. The intent is to not display SFrame related warnings or errors like: as_bad (_(".sframe not supported for target")); for unsupported targets if --enable-default-sframe is in effect. This implies we need to have a four state enum ( GEN_SFRAME_DEFAULT_NONE, GEN_SFRAME_CONFIG_ENABLED, GEN_SFRAME_DISABLED, GEN_SFRAME_ENABLED) gas -- You are receiving this mail because: You are on the CC list for the bug.
