From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Joern Rennecke <joern.rennecke@embecosm.com>
Cc: Joel Sherrill <Joel.Sherrill@oarcorp.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Michael Eager <eager@eagercon.com>
Subject: Re: [buildrobot] microblaze-elf / microblaze-linux
Date: Tue, 26 Nov 2013 15:28:00 -0000 [thread overview]
Message-ID: <20131126152755.GR30563@lug-owl.de> (raw)
In-Reply-To: <CAMqJFCqcAz1JD0CyaPNTEh0J6svCRc7rvr8KskOowWtREk34yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
On Tue, 2013-11-26 15:21:12 +0000, Joern Rennecke <joern.rennecke@embecosm.com> wrote:
> On 26 November 2013 14:51, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > On Tue, 2013-11-26 06:33:39 -0600, Joel Sherrill <Joel.Sherrill@OARcorp.com> wrote:
> > > Was microblaze-rtems attempted? I would have expected a failure
> > > like these if so.
> >
> > No, it wasn't. It's not on the list of targets in
> > .../gcc/contrib/config-list.mk . So we'd probably add that to the
> > target list I guess? I'll propose a patch later tonight (adding
> > to another pending patch to config-list.mk)
>
> The idea if config-list.mk is not to build every conceivable target
> configuration, but to give a reasonable converage of the different
> target architectures and OS/library configurations so that you can
> effectively test a patch with unknown target-specific impact.
Is it like that? My impression is/was that people collected a list of
targets they somewhat care for. With around 200 configurations, among
them some that are quite similar, adding another just adds 1/2%, which
I'd call neglectible.
> Is there something that microblaze-rtems exposes that is not already
> covered by other microblaze or rtems targets that are already included?
Probably not (without having looked at what that configuration would
actually pull in.)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: Alles wird gut! ...und heute wirds schon ein bißchen besser.
the second :
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-26 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 12:35 Joel Sherrill
2013-11-26 14:51 ` Jan-Benedict Glaw
2013-11-26 15:21 ` Joern Rennecke
2013-11-26 15:28 ` Jan-Benedict Glaw [this message]
2013-11-26 16:03 ` Michael Eager
2013-11-26 16:52 ` Joseph S. Myers
2013-11-26 17:38 ` Joel Sherrill
2013-11-26 18:00 ` Ralf Corsepius
2013-11-26 18:54 ` Joel Sherrill
2013-11-26 19:50 ` Joern Rennecke
2013-11-26 19:54 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2013-11-26 3:20 [buildrobot] First results of running contrib/config-list.mk Jan-Benedict Glaw
2013-11-26 3:27 ` [buildrobot] microblaze-elf / microblaze-linux Jan-Benedict Glaw
2013-11-26 15:51 ` Michael Eager
2013-11-26 16:08 ` Jan-Benedict Glaw
2013-11-26 16:13 ` Michael Eager
2013-11-26 16:17 ` Jan-Benedict Glaw
2013-11-26 17:16 ` Michael Eager
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=20131126152755.GR30563@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=Joel.Sherrill@oarcorp.com \
--cc=eager@eagercon.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).