From: Jeff Law <law@redhat.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: "Moore, Catherine" <Catherine_Moore@mentor.com>,
Denis Chertykov <chertykov@gmail.com>,
Eric Christopher <echristo@gmail.com>,
Matthew Fortune <matthew.fortune@imgtec.com>,
David Edelsohn <dje.gcc@gmail.com>,
Alexandre Oliva <aoliva@redhat.com>,
Kaz Kojima <kkojima@gcc.gnu.org>,
Oleg Endo <olegendo@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [BUILDROBOT] "error: null argument where non-null required" on multiple targets
Date: Thu, 17 Dec 2015 18:05:00 -0000 [thread overview]
Message-ID: <5672F976.1090609@redhat.com> (raw)
In-Reply-To: <20151216104603.GB27807@lug-owl.de>
On 12/16/2015 03:46 AM, Jan-Benedict Glaw wrote:
> On Tue, 2015-12-15 10:43:58 -0700, Jeff Law <law@redhat.com> wrote:
>> On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote:
>>> On Mon, 2015-12-14 18:54:28 +0000, Moore, Catherine <Catherine_Moore@mentor.com> wrote:
>>>>> avr-rtems http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478544
>>>>> mipsel-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478844
>>>>> mipsisa64r2-sde-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478855
>>>>> mipsisa64sb1-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478865
>>>>> mips-rtems http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478877
>>>>> powerpc-eabialtivec http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478922
>>>>> powerpc-eabispe http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478932
>>>>> powerpc-rtems http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478956
>>>>> ppc-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478968
>>>>> sh-superh-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=479077
>>>>
>>>> Is there an easy way to reproduce the MIPS problems that you
>>>> reported? I don't seem to be able to do it with a cross-compiler
>>>> targeting mipsel-elf.
>>>
>>> What's your build compiler? For these builds, where it showed up, I'm
>>> using a freshly compiles HEAD/master version. So basically, compile a
>>> current GCC for your build machine:
>> Right. This is something that only shows up when using the trunk to build
>> the crosses.
>>
>> When I looked, I thought I bisected it to the delayed folding work.
>
> Shall I bisect one of the cases anew, with the "Test value of
> _GLIBCXX_USE_C99_WCHAR not whether it is defined" patch that uncovered
> it, applied? Starting with some arbitrary old revision?
Yes. I'd really like to see config-list.mk working again. The first
step is always building a test the developers can easily work with.
jeff
next prev parent reply other threads:[~2015-12-17 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 21:48 Jan-Benedict Glaw
2015-12-14 18:54 ` Moore, Catherine
2015-12-14 20:07 ` Jan-Benedict Glaw
2015-12-15 17:44 ` Jeff Law
2015-12-16 10:46 ` Jan-Benedict Glaw
2015-12-17 18:05 ` Jeff Law [this message]
2015-12-17 18:34 ` config-list.mk and obsoleted configurations (was: [BUILDROBOT] "error: null argument where non-null required" on multiple targets) Jan-Benedict Glaw
2015-12-17 18:39 ` config-list.mk and obsoleted configurations Jeff Law
2015-12-17 18:58 ` Jan-Benedict Glaw
2015-12-17 19:53 ` Jeff Law
2015-12-17 20:33 ` Trevor Saunders
2015-12-17 21:02 ` Jeff Law
2015-12-21 14:20 ` [BUILDROBOT] "error: null argument where non-null required" on multiple targets Moore, Catherine
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=5672F976.1090609@redhat.com \
--to=law@redhat.com \
--cc=Catherine_Moore@mentor.com \
--cc=aoliva@redhat.com \
--cc=chertykov@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=echristo@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=jwakely@redhat.com \
--cc=kkojima@gcc.gnu.org \
--cc=matthew.fortune@imgtec.com \
--cc=olegendo@gcc.gnu.org \
/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).