On Fri, Apr 25, 2025 at 3:06 PM Andi Kleen wrote:
>
> On 2025-04-23 10:18, Richard Biener wrote:
> > On Tue, Apr 22, 2025 at 5:43 PM Andi Kleen wrote:
> >>
> >> On 2025-04-22 13:22, Richard Biener wrote:
> >> > On Sat, Apr 12, 2025 at 5:09 PM Andi Kleen wrote:
> >> >>
> >> >> From: Andi Kleen
>
On 2025-04-23 10:18, Richard Biener wrote:
On Tue, Apr 22, 2025 at 5:43 PM Andi Kleen wrote:
On 2025-04-22 13:22, Richard Biener wrote:
> On Sat, Apr 12, 2025 at 5:09 PM Andi Kleen wrote:
>>
>> From: Andi Kleen
>>
>> ... that uses -march=native -mtune=native to build a compiler
>> optimized
> -Original Message-
> From: Jakub Jelinek
> Sent: Wednesday, April 23, 2025 10:39 AM
> To: Tamar Christina
> Cc: Richard Biener ; Andi Kleen
> ; GCC Patches
> Subject: Re: [PATCH] Add a bootstrap-native build config
>
> On Wed, Apr 23, 2025 at 09:36:11AM +
On Wed, Apr 23, 2025 at 10:05:25AM +, Tamar Christina wrote:
> > -Original Message-
> > From: Jakub Jelinek
> > Sent: Wednesday, April 23, 2025 10:39 AM
> > To: Tamar Christina
> > Cc: Richard Biener ; Andi Kleen
> > ; GCC Patches
> > S
On Wed, Apr 23, 2025 at 09:36:11AM +, Tamar Christina wrote:
> On AArch64 it does but only if no other
> tuning options are specified.
That is the case on x86 as well, -march=native -mtune=znver5 will
still tune for znver5, but -march=native will tune for native.
Jakub
> -Original Message-
> From: Richard Biener
> Sent: Wednesday, April 23, 2025 9:19 AM
> To: Andi Kleen ; GCC Patches
> Subject: Re: [PATCH] Add a bootstrap-native build config
>
> On Tue, Apr 22, 2025 at 5:43 PM Andi Kleen wrote:
> >
> > On 2025-
On Tue, Apr 22, 2025 at 5:43 PM Andi Kleen wrote:
>
> On 2025-04-22 13:22, Richard Biener wrote:
> > On Sat, Apr 12, 2025 at 5:09 PM Andi Kleen wrote:
> >>
> >> From: Andi Kleen
> >>
> >> ... that uses -march=native -mtune=native to build a compiler
> >> optimized
> >> for the host.
> >
> > -mar
On Sat, Apr 12, 2025 at 5:09 PM Andi Kleen wrote:
>
> From: Andi Kleen
>
> ... that uses -march=native -mtune=native to build a compiler optimized
> for the host.
-march=native implies -mtune=native so I think the latter is redundant.
> config/ChangeLog:
>
> * bootstrap-native.mk: New f
On Tue, Jul 30, 2024 at 09:40:42AM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> ... that uses -march=native -mtune=native to build a compiler optimized
> for the host.
>
> config/ChangeLog:
>
> * bootstrap-native.mk: New file.
>
> gcc/ChangeLog:
>
> * doc/install.texi: Document
On Tue, 30 Jul 2024, Andi Kleen wrote:
> config/ChangeLog:
>
> * bootstrap-native.mk: New file.
>
> gcc/ChangeLog:
>
> * doc/install.texi: Document bootstrap-native.
This makes sense to me, and the documentation is fine (with "latter"
instead of "later"); I cannot approve the code
> > +BOOT_CFLAGS := -march=native -mtune=native $(BOOT_CFLAGS)
>
> I was under the impression that -mtune=native is useless with
> -march=native. Is that wrong?
On x86 it's right, but not sure about other architectures. I suppose
it doesn't hurt.
-Andi
Andi Kleen writes:
> From: Andi Kleen
>
> ... that uses -march=native -mtune=native to build a compiler optimized
> for the host.
>
I like the idea and I'll probably use this. (I can't approve it though.)
> config/ChangeLog:
>
> * bootstrap-native.mk: New file.
>
> gcc/ChangeLog:
>
>
12 matches
Mail list logo