From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: add sparc64 architecture support
Date: Sat, 29 Aug 2015 10:11:36 +0200 [thread overview]
Message-ID: <20150829101136.02a50aec@free-electrons.com> (raw)
In-Reply-To: <20150829074104.GB8475@waldemar-brodkorb.de>
Waldemar,
On Sat, 29 Aug 2015 09:41:04 +0200, Waldemar Brodkorb wrote:
> Yeah, the main reason providing the patch is to discover portability
> issues in software packages for this platform. I like the
> autobuilder stuff and a greater test coverage is useful in my
> opinion.
Ok, no problem.
> There is already ppc64-pseries, which isn't an embedded system or do
> I missed something? :=)
Yes, it was contributed by IBM IIRC, so we kind of assumed they would
be around to fix issues if any (though in practice we have not yet
added a PowerPC 64 toolchain configuration in the autobuilders, so my
comment is a bit moot as we have never tested the reactivity of the IBM
guys).
> > > config BR2_ENDIAN
> > > default "BIG"
> > > @@ -20,3 +24,4 @@ config BR2_ENDIAN
> > > config BR2_GCC_TARGET_CPU
> > > default "leon3" if BR2_sparc_leon3
> > > default "v8" if BR2_sparc_v8
> > > + default "ultrasparc" if BR2_sparc_v9
> >
> > Why not using v9 here? It's a valid -mcpu value:
>
> Valid, but not useful for Linux:
> http://permalink.gmane.org/gmane.comp.lib.glibc.alpha/10649
So maybe the option should be called v9a, rather than just v9 ? Or just
Ultrasparc so it matches the name of the gcc -mcpu option ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-29 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 20:37 [Buildroot] [PATCH 1/2] toolchain: add sparc64 architecture support Waldemar Brodkorb
2015-08-27 18:27 ` Waldemar Brodkorb
2015-08-28 18:22 ` Thomas Petazzoni
[not found] ` <20150829074104.GB8475@waldemar-brodkorb.de>
2015-08-29 8:11 ` Thomas Petazzoni [this message]
2015-10-08 14:08 ` Gustavo Zacarias
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=20150829101136.02a50aec@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox