Hi Richard,
> I specifically want to test generic SVE rather than SVE tuned for a
> specific core, so --with-arch=armv8.2-a+sve is the thing I want to test.
Btw that's not actually what you get if you use cc1 - you always get armv8.0,
so --with-arch doesn't work at all. The only case that
Hi Richard,
>>> I share Richard E's concern about the effect of this on people who run
>>> ./cc1 directly. (And I'm being selfish here, because I regularly run
>>> ./cc1 directly on toolchains configured with --with-arch=armv8.2-a+sve.)
>>> So TBH my preference would be to keep the
Wilco Dijkstra via Gcc-patches writes:
> Hi Richard,
>
>> I share Richard E's concern about the effect of this on people who run
>> ./cc1 directly. (And I'm being selfish here, because I regularly run
>> ./cc1 directly on toolchains configured with --with-arch=armv8.2-a+sve.)
>> So TBH my
Hi Richard,
> I share Richard E's concern about the effect of this on people who run
> ./cc1 directly. (And I'm being selfish here, because I regularly run
> ./cc1 directly on toolchains configured with --with-arch=armv8.2-a+sve.)
> So TBH my preference would be to keep the
"Pop, Sebastian" writes:
> On 11/19/20, 10:52 AM, "Richard Earnshaw (lists)"
> wrote:
>> Having the same option have a completely different meaning would be even
>> worse than not having the option at all. So no, that's a non-starter.
>
> The attached patch 0001 removes
On 11/19/20, 10:52 AM, "Richard Earnshaw (lists)"
wrote:
> Having the same option have a completely different meaning would be even
> worse than not having the option at all. So no, that's a non-starter.
The attached patch 0001 removes --with-{cpu,arch,tune}-32.
Bootstrap and regression
On 19/11/2020 14:40, Wilco Dijkstra via Gcc-patches wrote:
> Hi,
>
As for your second patch, --with-cpu-64 could be a simple alias indeed,
but what is the exact definition/expected behaviour of a --with-cpu-32
on a target that only supports 64-bit code? The AArch64
Hi,
>>> As for your second patch, --with-cpu-64 could be a simple alias indeed,
>>> but what is the exact definition/expected behaviour of a --with-cpu-32
>>> on a target that only supports 64-bit code? The AArch64 target cannot
>>> generate AArch32 code, so we shouldn't silently
On 18/11/2020 17:16, Pop, Sebastian via Gcc-patches wrote:
> Hi,
>
> On 11/18/20, 10:17 AM, "Wilco Dijkstra" wrote:
>>I presume you're trying to unify the --with- options across most targets?
>
> Yes, my intention was to provide the same configure options on arm64
> as on x86, such that
Hi,
On 11/18/20, 10:17 AM, "Wilco Dijkstra" wrote:
>I presume you're trying to unify the --with- options across most targets?
Yes, my intention was to provide the same configure options on arm64
as on x86, such that projects that already use those options can change
cpu name to
Hi Sebastian,
I presume you're trying to unify the --with- options across most targets?
That would be very useful! However there are significant differences between
targets in how they interpret options like --with-arch=native (or -march). So
those differences also need to be looked at and fixed
On 11/17/20 2:27 PM, Pop, Sebastian via Gcc-patches wrote:
> Hi,
>
> here is a follow-up patch to add missing Arm64 configure flags as aliases to
> the existing flags.
>
> gcc/
> * config.gcc: add configure flags --with-{cpu,arch,tune}-{32,64}
> as alias flags for
On 11/17/20 10:53 AM, Pop, Sebastian via Gcc-patches wrote:
> Hi,
>
> the attached patch fixes a configure error on Arm64 when passing
> --with-tune=... to configure:
> ```
> This target does not support --with-tune.
> Valid --with options are: abi cpu arch
> ```
> The missing flag sets target
Hi,
here is a follow-up patch to add missing Arm64 configure flags as aliases to
the existing flags.
gcc/
* config.gcc: add configure flags --with-{cpu,arch,tune}-{32,64}
as alias flags for --with-{cpu,arch,tune} on AArch64.
* doc/install.texi: Document new flags for
Hi,
the attached patch fixes a configure error on Arm64 when passing
--with-tune=... to configure:
```
This target does not support --with-tune.
Valid --with options are: abi cpu arch
```
The missing flag sets target tuning to a different value than the generic
tuning.
gcc/
*
15 matches
Mail list logo
