This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Prototype of hook for possible list of option values.

On 20/07/18 12:06, Martin Liška wrote:
> On 07/20/2018 12:58 PM, Richard Earnshaw (lists) wrote:
>> Modifiers are context dependent.  The architecture implies which
>> modifiers can be applied (and what they mean in detail, so, for example,
>> +fp means enable the default floating point variant for this
>> architecture).  Not all modifiers apply to all architectures - +fp is
>> not permitted on ARMv4t, for example.
> I see, that said I would really add just the target hook suggested. It will
> help people in bash completions and provide reasonable list in --help output.
> More complex approaches are possible, but don't worth in my opinion.
> If you agree, I can clean up the API and improve documentatio?
> Martin

I do wonder if it would be helpful for the API to be able to provide a
'prefix value' for prematching.  So that, for example,


would pass 'cortex' as a pre-match and then the compiler could supply
just the valid cpus that start with cortex.  or


would pass 'cortex-a5+' and the compiler can supply the valid extensions
to that CPU.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]