All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Larsson <andreas@gaisler.com>
To: buildroot@busybox.net
Subject: [Buildroot] Sparc Leon support in Buildroot
Date: Wed, 20 Aug 2014 13:01:33 +0200	[thread overview]
Message-ID: <53F4800D.2060307@gaisler.com> (raw)
In-Reply-To: <20140701202206.153b2cf6@free-electrons.com>

On 2014-07-01 20:22, Thomas Petazzoni wrote:
> Hello Konrad,
>
> Back in 2010, you contributed a number of patches to Buildroot to
> support the Sparc Leon processors. It turns out that today, those
> processors are the only one still needing gcc 4.4.x:
>
>          prompt "GCC compiler Version"
>          default BR2_GCC_VERSION_4_4_X if BR2_sparc_sparchfleon || BR2_sparc_sparchfleonv8 || BR2_sparc_sparcsfleon || BR2_sparc_sparcsfleonv8
>          default BR2_GCC_VERSION_4_2_2_AVR32_2_1_5 if BR2_avr32
>          default BR2_GCC_VERSION_4_7_X if BR2_sparc
>          default BR2_GCC_VERSION_4_8_ARC if BR2_arc
>          default BR2_GCC_VERSION_4_9_X if BR2_microblaze || BR2_powerpc64le
>          default BR2_GCC_VERSION_4_5_X if BR2_bfin
>          default BR2_GCC_VERSION_4_8_X
>
> Do you know if there's any reason to still keep gcc 4.4 for those
> processors? Wasn't the support for Sparc Leon merged in upstream gcc?
>  From https://sourceware.org/ml/crossgcc/2011-12/msg00004.html, I see
> that some patches were still needed for gcc 4.6, but according to
> https://gcc.gnu.org/onlinedocs/gcc/SPARC-Options.html, Sparc Leon
> processors seem to be supported.
>
> According to https://gcc.gnu.org/gcc-4.6/changes.html, the Sparc Leon
> supported was merged in gcc 4.6: "GCC now supports the LEON series of
> SPARC V8 processors. The code generated by the compiler can either be
> tuned to it by means of the --with-tune=leon configure option and
> -mtune=leon compilation option, or the compiler can be built for the
> sparc-leon-{elf,linux} and sparc-leon3-{elf,linux} targets directly.".
>
> Could you update us on the Sparc Leon support, and maybe submit some
> patches to Buildroot to make the relevant changes?


Hi!

I am looking into this and will submit some patches.

Best regards,

Andreas Larsson
Software Engineer
Aeroflex Gaisler AB
Aeroflex Microelectronic Solutions ? HiRel
Kungsgatan 12
SE-411 19 Gothenburg, Sweden
Phone: +46 31 7758669
andreas at gaisler.com
www.Aeroflex.com/Gaisler

  reply	other threads:[~2014-08-20 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 18:22 [Buildroot] Sparc Leon support in Buildroot Thomas Petazzoni
2014-08-20 11:01 ` Andreas Larsson [this message]
2014-08-20 12:05   ` Thomas Petazzoni
2014-09-03 14:13     ` Andreas Larsson
2014-09-03 14:45       ` Thomas Petazzoni
2014-09-03 15:14         ` Andreas Larsson

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=53F4800D.2060307@gaisler.com \
    --to=andreas@gaisler.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.