Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: opendmb@gmail.com, mmayer@broadcom.com, buildroot@buildroot.org,
	"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/2] toolchain/Config.in: add BR2_TOOLCHAIN_GCC_AT_LEAST_12 blind option
Date: Tue, 26 Apr 2022 20:42:33 +0200	[thread overview]
Message-ID: <20220426204233.77ed8bc5@windsurf> (raw)
In-Reply-To: <20220426173211.64840-2-f.fainelli@gmail.com>

Hello Florian,

Thanks for the patch! I hope you're doing well :-)

On Tue, 26 Apr 2022 10:32:10 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:

> In order to add gcc 12 support for internal and external toolchain
> in follow-up commits, introduce BR2_TOOLCHAIN_GCC_AT_LEAST_12 symbol.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  toolchain/Config.in | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index d2c81217c84a..b572a89f2f85 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -117,7 +117,8 @@ config BR2_TOOLCHAIN_HAS_GCC_BUG_43744
>  	depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_8 || \
>  		BR2_TOOLCHAIN_GCC_AT_LEAST_9 || \
>  		BR2_TOOLCHAIN_GCC_AT_LEAST_10 || \
> -		BR2_TOOLCHAIN_GCC_AT_LEAST_11
> +		BR2_TOOLCHAIN_GCC_AT_LEAST_11 || \
> +		BR2_TOOLCHAIN_GCC_AT_LEAST_12
>  
>  # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63261. This bug no
>  # longer exists in gcc 8.x.
> @@ -150,7 +151,8 @@ config BR2_TOOLCHAIN_HAS_GCC_BUG_68485
>  config BR2_TOOLCHAIN_HAS_GCC_BUG_83143
>  	bool
>  	default y if BR2_sh
> -	depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_10 || BR2_TOOLCHAIN_GCC_AT_LEAST_11
> +	depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_10 || BR2_TOOLCHAIN_GCC_AT_LEAST_11 || \
> +		   BR2_TOOLCHAIN_GCC_AT_LEAST_12

Did you verify that these two bugs still affected gcc 12.x ?

Thanks,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-26 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 17:32 [Buildroot] [PATCH v2 0/2] External GCC12 toolchain support Florian Fainelli
2022-04-26 17:32 ` [Buildroot] [PATCH v2 1/2] toolchain/Config.in: add BR2_TOOLCHAIN_GCC_AT_LEAST_12 blind option Florian Fainelli
2022-04-26 18:42   ` Thomas Petazzoni via buildroot [this message]
2022-04-26 22:32     ` Florian Fainelli
2022-04-26 17:32 ` [Buildroot] [PATCH v2 2/2] toolchain/toolchain-external/toolchain-external-custom: add gcc 12 version selection Florian Fainelli
2022-04-27 19:00 ` [Buildroot] [PATCH v2 0/2] External GCC12 toolchain support Arnout Vandecappelle
2022-04-27 23:59   ` Florian Fainelli

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=20220426204233.77ed8bc5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=f.fainelli@gmail.com \
    --cc=mmayer@broadcom.com \
    --cc=opendmb@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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