Re: [PATCH] gas: Add --compress-debug-sections=force

[Jan Beulich <jbeulich@suse.com>]

On 27.02.2023 12:43, Tom de Vries wrote:
> On 2/27/23 10:03, Jan Beulich wrote:
>> But I guess whether that's really
>> needed first of all depends on the semantics we want e.g.
>>
>> --nocompress-debug-sections --compress-debug-sections=force
>>
>> to have (which, with how you have it presently, could also be expressed
>> as
>>
>> --compress-debug-sections=none+force
>>
>> or
>>
>> --compress-debug-sections=none --compress-debug-sections=force
>>
>> afaict). I view the present meaning as one sensible one, but I could
>> also see "none" (or equivalent) simply zapping the compression type
>> (and hence rendering "force" meaningless) as another sensible one.
> 
> Sure, that's another possible semantics.
> 
> Should I implement that instead?

Not sure - as said, depends on what exactly is wanted. I find both
variants leaving too much room for ambiguity, so I can't really decide
(for myself).

>> A
>> change in meaning may then also result in the three option combinations
>> above possibly not all doing the same.
>>
> 
>> As an aside: As you update the patch, please try to keep the title in
>> line with what the patch actually does.
>>
> 
> I'm assuming you mean the email title (the patch title looks ok to me), 
> and I've updated it.

Hmm, yes, sorry - I'm normally implying new patch versions to be at
the root of new threads (and with increased version number), not in
reply to earlier versions. Hence I didn't pay attention to the Re: ...
still being there from the initial patch.

Jan