On Tue, 2013-11-26 19:50:10 +, Joern Rennecke
wrote:
> On 26 November 2013 17:38, Joel Sherrill wrote:
> > as to Joern's question:
> > > Is there something that microblaze-rtems exposes that is not
> > > already covered by other microblaze or rtems targets that are
> > > already included?
>
On 26 November 2013 17:38, Joel Sherrill wrote:
> The key to seeing the value of testing *-rtems is moving
> beyond "builds or not" and into running tests on more
> languages.
Well, we are already configuring with --enable-languages=all,ada,go ,
so there are a lot of frontends being build - just
On 11/26/2013 11:58 AM, Ralf Corsepius wrote:
> On 11/26/2013 06:38 PM, Joel Sherrill wrote:
>
>>> Is there something that microblaze-rtems exposes that is not already
>>> covered by other microblaze or rtems targets that are already included?
>>
>> I believe it was on the microblaze where someone
On 11/26/2013 06:38 PM, Joel Sherrill wrote:
Is there something that microblaze-rtems exposes that is not already
covered by other microblaze or rtems targets that are already included?
I believe it was on the microblaze where someone broke the
libgcc pattern for rtems by changing the pattern
On 11/26/2013 10:52 AM, Joseph S. Myers wrote:
> On Tue, 26 Nov 2013, Jan-Benedict Glaw wrote:
>
>>> 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
On 11/26/13 08:16, Jan-Benedict Glaw wrote:
On Tue, 2013-11-26 08:13:12 -0800, Michael Eager wrote:
On 11/26/13 08:08, Jan-Benedict Glaw wrote:
Thanks for looking into the issue anyways! (...and what do you
think about adding a microblazeel target to the list?)
Sounds OK to me.
Any sugges
On Tue, 26 Nov 2013, Jan-Benedict Glaw wrote:
> > 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 unk
On 11/26/13 08:08, Jan-Benedict Glaw wrote:
On Tue, 2013-11-26 07:50:34 -0800, Michael Eager wrote:
On 11/25/13 19:26, Jan-Benedict Glaw wrote:
Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=4071
On Tue, 2013-11-26 08:13:12 -0800, Michael Eager wrote:
> On 11/26/13 08:08, Jan-Benedict Glaw wrote:
> > Thanks for looking into the issue anyways! (...and what do you
> > think about adding a microblazeel target to the list?)
>
> Sounds OK to me.
Any suggestion of which target(s) to choose?
On Tue, 2013-11-26 07:50:34 -0800, Michael Eager wrote:
> On 11/25/13 19:26, Jan-Benedict Glaw wrote:
> > Build logs at
> > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
> > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
> >
> > (I also think that we'd
On 11/26/13 07:27, Jan-Benedict Glaw wrote:
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.)
I believe that micr
On 11/25/13 19:26, Jan-Benedict Glaw wrote:
Hi!
Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
(I also think that we'd have the little endian version on the target
list at contrib/config-lis
On Tue, 2013-11-26 15:21:12 +, Joern Rennecke
wrote:
> On 26 November 2013 14:51, Jan-Benedict Glaw wrote:
> > On Tue, 2013-11-26 06:33:39 -0600, Joel Sherrill
> > wrote:
> > > Was microblaze-rtems attempted? I would have expected a failure
> > > like these if so.
> >
> > No, it wasn't. I
On 26 November 2013 14:51, Jan-Benedict Glaw wrote:
> On Tue, 2013-11-26 06:33:39 -0600, Joel Sherrill
> 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 w
On Tue, 2013-11-26 06:33:39 -0600, Joel Sherrill
wrote:
> Jan-Benedict Glaw wrote:
> > Build logs at
> > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
> > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
> >
> > (I also think that we'd have the little
Was microblaze-rtems attempted? I would have expected a failure like these if
so.
--joel
Jan-Benedict Glaw wrote:
Hi!
Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
(I also think that we
Hi!
Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
(I also think that we'd have the little endian version on the target
list at contrib/config-list.mk ...)
g++ -c -g -O2 -DIN_GCC -DCROSS_
17 matches
Mail list logo
