From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] arch/Config.in.x86: add option for -march=x86-64
Date: Sun, 9 Jan 2022 11:33:51 +0100 [thread overview]
Message-ID: <20220109103351.GJ1881783@scaer> (raw)
In-Reply-To: <20220109080124.2271241-1-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2022-01-09 09:01 +0100, Thomas Petazzoni spake thusly:
> We already have support for a wide range of x86-64 CPUs, but we don't
> have any option to build for the most generic possible x86-64 CPU, as
> made available by the -march=x86-64 GCC option.
As discussed, it only really makes sense to use them as a 64-bit CPU, so
I've added a dependency on BR2_x86_64.
> This commit makes this option available in Buildroot.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> arch/Config.in.x86 | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/Config.in.x86 b/arch/Config.in.x86
> index 7aae3cafb7..794d808d96 100644
> --- a/arch/Config.in.x86
> +++ b/arch/Config.in.x86
> @@ -81,6 +81,16 @@ config BR2_x86_prescott
> select BR2_X86_CPU_HAS_SSE
> select BR2_X86_CPU_HAS_SSE2
> select BR2_X86_CPU_HAS_SSE3
> +config BR2_x86_x86_64
> + bool "x86-64"
> + select BR2_X86_CPU_HAS_MMX
> + select BR2_X86_CPU_HAS_SSE
> + select BR2_X86_CPU_HAS_SSE2
> + help
> + This option corresponds to -march=x86-64, documented as a
> + "Generic CPU with 64-bit extensions" by the GCC
> + documentation. It is a 64-bit CPU with MMX, SSE and SSE2
> + support.
> config BR2_x86_nocona
> bool "nocona"
> select BR2_X86_CPU_HAS_MMX
> @@ -281,6 +291,7 @@ config BR2_GCC_TARGET_ARCH
> default "pentium3" if BR2_x86_pentium3
> default "pentium4" if BR2_x86_pentium4
> default "prescott" if BR2_x86_prescott
> + default "x86-64" if BR2_x86_x86_64
> default "nocona" if BR2_x86_nocona
> default "core2" if BR2_x86_core2
> default "corei7" if BR2_x86_corei7
> --
> 2.33.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-09 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 8:01 [Buildroot] [PATCH 1/2] arch/Config.in.x86: add option for -march=x86-64 Thomas Petazzoni
2022-01-09 8:01 ` [Buildroot] [PATCH 2/2] arch/Config.in.x86: add support for x86-64-v2, x86-64-v3, x86-64-v4 Thomas Petazzoni
2022-01-09 10:36 ` Yann E. MORIN
2022-01-09 10:46 ` Romain Naour
2022-01-09 10:33 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220109103351.GJ1881783@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox