public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Denis Chertykov <chertykov@gmail.com>,
	Catherine Moore <clm@codesourcery.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>
Cc: Jonathan Wakely <jwakely@redhat.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [BUILDROBOT] "error: null argument where non-null required" on multiple targets
Date: Sun, 06 Dec 2015 21:48:00 -0000	[thread overview]
Message-ID: <20151206214848.GA495@lug-owl.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 3075 bytes --]

Hi!

I'm not 100% sure, but I *think* that this patch

	2015-11-15  Jonathan Wakely  <jwakely@redhat.com>
	
		PR libstdc++/68353
		* include/bits/basic_string.h: Test value of _GLIBCXX_USE_C99_WCHAR
		not whether it is defined.
		* include/ext/vstring.h: Likewise.

uncovered errors like this:

/---------------------------------------
| g++ -fno-PIE -c  -DIN_GCC_FRONTEND -DIN_GCC_FRONTEND -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -Ic-family -I../../../gcc/gcc -I../../../gcc/gcc/c-family -I../../../gcc/gcc/../include -I../../../gcc/gcc/../libcpp/include -I/opt/cfarm/mpc/include  -I../../../gcc/gcc/../libdecnumber -I../../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I../../../gcc/gcc/../libbacktrace   -o c-family/c-common.o -MT c-family/c-common.o -MMD -MP -MF c-family/.deps/c-common.TPo ../../../gcc/gcc/c-family/c-common.c
| In file included from ../../../gcc/gcc/c-family/c-common.c:31:0:
| ../../../gcc/gcc/c-family/c-common.c: In function ‘void c_common_nodes_and_builtins()’:
| ../../../gcc/gcc/stringpool.h:39:53: error: null argument where non-null required (argument 1) [-Werror=nonnull]
|      ? get_identifier_with_length ((str), strlen (str))  \
|                                                      ^
| 
| ../../../gcc/gcc/c-family/c-common.c:5501:22: note: in expansion of macro ‘get_identifier’
|    char32_type_node = get_identifier (CHAR32_TYPE);
|                       ^~~~~~~~~~~~~~
| 
| cc1plus: all warnings being treated as errors
| Makefile:1085: recipe for target 'c-family/c-common.o' failed
\---------------------------------------

Shows up when using a newly build compiler to build the
contrib/config-list.mk targets. So these targets probably need some
small touch-ups.

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

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
 Signature of:                    Don't believe in miracles: Rely on them!
 the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2015-12-06 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 21:48 Jan-Benedict Glaw [this message]
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
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=20151206214848.GA495@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=aoliva@redhat.com \
    --cc=chertykov@gmail.com \
    --cc=clm@codesourcery.com \
    --cc=dje.gcc@gmail.com \
    --cc=echristo@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).