[PATCH v2] gas: support --gsframe=no

[Jan Beulich]

On 14.07.2025 20:06, Indu Bhagat wrote:
> On 7/12/25 1:59 PM, Sam James wrote:
>> Indu Bhagat <indu.bhagat@oracle.com> writes:
>>> On 7/11/25 9:45 AM, Sam James wrote:
>>>> --- a/gas/as.c
>>>> +++ b/gas/as.c
>>>> @@ -311,7 +311,8 @@ Options:\n\
>>>>      fprintf (stream, _("\
>>>>                              generate GNU Build notes if none are present in the input\n"));
>>>>      fprintf (stream, _("\
>>>> -  --gsframe               generate SFrame stack trace information\n"));
>>>> +  --gsframe=[no|yes]      whether to generate SFrame stack trace information\n\
>>>> +                          (default: no)\n"));
>>>
>>> (default: yes)
>>
>> The default is no if you pass nothing, but the default is yes if
>> you pass --gsframe..
>>
> OK.  So the default of --gsframe is equivalent to --gsframe=yes. 
> Meaning the default is yes if you pass --gsframe.  Agreed.  But this 
> contradicts ...
> 
>> In my other (yet-unposted) patch to allow default-enabling of SFrames
>> via configure, I make the 'no' dependent on whatever I chose at
>> configure-time.
>>
> 
>> If we interpret the 'default: XXX' value as being "what does --gsframe
>> do", then in that case, it'll always say no, I think?
>>
> 
> ...this one.
> 
> If we interpret 'default: XXX' value as "what does --gsframe do", the 
> default is a yes.

Hmm, but generally the defaults mentioned in help output aren't what
the option without argument means, but how gas behaves when the option
isn't passed at all.

Jan