Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: ARC Maintainers <arc-buildroot@synopsys.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gcc: restrict hs4x_rel31 to arc gcc fork
Date: Tue, 17 May 2022 00:16:06 +0200	[thread overview]
Message-ID: <ea7b7264-e6a6-0093-4ffb-735edba718dd@gmail.com> (raw)
In-Reply-To: <20220516214438.GL1597494@scaer>

Hello Yann,

Le 16/05/2022 à 23:44, Yann E. MORIN a écrit :
> On 2022-05-15 21:36 +0200, Romain Naour spake thusly:
>> ARC hs4x_rel31 cpu is not supported by upstream gcc version.
>> Only the generic HS48 processor (BR2_archs4x) is supported
>> by upstream gcc.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/357a74d53af96d4b868a9d5b9f9ce9432e0c53b5
>> http://autobuild.buildroot.net/results/bcdf160a3d5ffcccd4402f65aca153faca4b32c2
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
>> Cc: ARC Maintainers <arc-buildroot@synopsys.com>
>> ---
>>  package/gcc/Config.in.host | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
>> diff --git a/package/gcc/Config.in.host b/package/gcc/Config.in.host
>> index f6b9b4fa9d..2b12035c4b 100644
>> --- a/package/gcc/Config.in.host
>> +++ b/package/gcc/Config.in.host
>> @@ -31,6 +31,8 @@ config BR2_GCC_VERSION_9_X
>>  	# upstream gcc. C-SKY gcc upstream support not tested
>>  	# with upstream binutils and glibc.
>>  	depends on !BR2_csky
>> +	# ARC HS48 rel 31 only supported by gcc arc fork.
>> +	depends on !BR2_archs4x_rel31
> 
> So, in the commit log, you say that BR2_archs4x is the only variant
> supported by upstream gcc, yet this change still allows all the hs38
> and the 7x0d variants to use the upstream gcc.

I'm only speaking about ARC hs48, not other ARC variant.

> 
> Did I misread the commit log, and you really meant:
> 
>     Of the hs48 series, only the generic HS48 processor (BR2_archs4x) is
>     supported by upstream gcc, while the hs48 rel31 (hs4x_rel31) is not,
>     and is only suppoerted by the ARC fork.
> 
>     All the other variants, 7x0d and hs38, are all supported in upstream
>     gcc.>
> Thoughts?

hs4x_rel31 seems the only one not supported by upstream gcc.

Best regards,
Romain


> 
> Regards,
> Yann E. MORIN.
> 
>>  	select BR2_TOOLCHAIN_GCC_AT_LEAST_9
>>  
>>  config BR2_GCC_VERSION_10_X
>> @@ -43,6 +45,8 @@ config BR2_GCC_VERSION_10_X
>>  	# upstream gcc. C-SKY gcc upstream support not tested
>>  	# with upstream binutils and glibc.
>>  	depends on !BR2_csky
>> +	# ARC HS48 rel 31 only supported by gcc arc fork.
>> +	depends on !BR2_archs4x_rel31
>>  	select BR2_TOOLCHAIN_GCC_AT_LEAST_10
>>  
>>  config BR2_GCC_VERSION_11_X
>> @@ -54,6 +58,8 @@ config BR2_GCC_VERSION_11_X
>>  	# that need to be reverted since gcc 8.4, 9.3 and 10.1.
>>  	# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
>>  	depends on !BR2_sparc
>> +	# ARC HS48 rel 31 only supported by gcc arc fork.
>> +	depends on !BR2_archs4x_rel31
>>  	select BR2_TOOLCHAIN_GCC_AT_LEAST_11
>>  
>>  endchoice
>> -- 
>> 2.35.3
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
> 

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-05-16 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 19:36 [Buildroot] [PATCH] package/gcc: restrict hs4x_rel31 to arc gcc fork Romain Naour
2022-05-16 21:44 ` Yann E. MORIN
2022-05-16 22:16   ` Romain Naour [this message]
2022-05-17 20:00 ` Yann E. MORIN
2022-05-29  8:43 ` Peter Korsgaard

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=ea7b7264-e6a6-0093-4ffb-735edba718dd@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=arc-buildroot@synopsys.com \
    --cc=buildroot@buildroot.org \
    --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