On 14/09/2020 20:04, Wilco Dijkstra wrote:
> Hi Richard,
>
>> On 14/09/2020 15:19, Wilco Dijkstra wrote:
>>> The --with-cpu/--with-arch configure option processing not only checks
>>> valid arguments
>>> but also sets TARGET_CPU_DEFAULT with a CPU and extension bitmask. This
>>> isn't used
>>>
Hi Richard,
>On 14/09/2020 15:19, Wilco Dijkstra wrote:
>> The --with-cpu/--with-arch configure option processing not only checks valid
>> arguments
>> but also sets TARGET_CPU_DEFAULT with a CPU and extension bitmask. This
>> isn't used
>> however since a --with-cpu is translated into a -mcpu
On 14/09/2020 15:19, Wilco Dijkstra wrote:
> The --with-cpu/--with-arch configure option processing not only checks valid
> arguments
> but also sets TARGET_CPU_DEFAULT with a CPU and extension bitmask. This
> isn't used
> however since a --with-cpu is translated into a -mcpu option which is
>
The --with-cpu/--with-arch configure option processing not only checks valid
arguments
but also sets TARGET_CPU_DEFAULT with a CPU and extension bitmask. This isn't
used
however since a --with-cpu is translated into a -mcpu option which is processed
as if
written on the command-line (so TARGET_