public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsg at openbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48851] lto-plugin.c:224:7: error: missing sentinel in function call [-Werror=format]
Date: Wed, 29 Jun 2011 21:18:00 -0000 [thread overview]
Message-ID: <bug-48851-4-fX3dnhfha7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48851-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48851
--- Comment #12 from Jonathan Gray <jsg at openbsd dot org> 2011-06-29 21:17:31 UTC ---
The problem appears to be in the "fixed" version of string.h
before:
#ifndef NULL
#ifdef __GNUG__
#define NULL __null
#else
#define NULL ((void *)0)
#endif
#endif
after:
#ifndef NULL
#ifdef __GNUG__
#define NULL __null
#else
#define NULL 0
#endif
#endif
fixincludes seems to be busted.
--- /usr/include/string.h Sat Jun 25 19:55:15 2011
+++ /home/jsg/src/obj461/./prev-gcc/include-fixed/string.h Wed Jun 29
01:33:27 2011
@@ -1,3 +1,12 @@
+/* DO NOT EDIT THIS FILE.
+
+ It has been auto-edited by fixincludes from:
+
+ "/usr/include/string.h"
+
+ This had to be done to correct non-standard usages in the
+ original, manufacturer supplied header file. */
+
/* $OpenBSD: string.h,v 1.21 2011/04/06 11:39:42 miod Exp $ */
/* $NetBSD: string.h,v 1.6 1994/10/26 00:56:30 cgd Exp $ */
@@ -47,7 +56,7 @@ typedef __size_t size_t;
#ifdef __GNUG__
#define NULL __null
#else
-#define NULL ((void *)0)
+#define NULL 0
#endif
#endif
bizarrely the same block in stddef.h is left alone by fixincludes
next prev parent reply other threads:[~2011-06-29 21:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 12:15 [Bug lto/48851] New: " michael.a.richmond at nasa dot gov
2011-05-03 13:49 ` [Bug lto/48851] " rguenth at gcc dot gnu.org
2011-05-03 14:14 ` michael.a.richmond at nasa dot gov
2011-05-03 14:27 ` froydnj at gcc dot gnu.org
2011-05-03 15:51 ` michael.a.richmond at nasa dot gov
2011-05-03 16:02 ` rguenth at gcc dot gnu.org
2011-05-03 16:10 ` jakub at gcc dot gnu.org
2011-05-03 16:25 ` schwab@linux-m68k.org
2011-05-04 11:05 ` rguenth at gcc dot gnu.org
2011-05-04 12:14 ` matz at gcc dot gnu.org
2011-06-29 8:31 ` jsg at openbsd dot org
2011-06-29 21:02 ` jsg at openbsd dot org
2011-06-29 21:18 ` jsg at openbsd dot org [this message]
2011-06-30 10:06 ` rguenth at gcc dot gnu.org
2011-06-30 10:13 ` jsg at openbsd dot org
2011-06-30 11:13 ` rguenth at gcc dot gnu.org
2011-06-30 12:19 ` jsg at openbsd dot org
2011-06-30 12:58 ` rguenth at gcc dot gnu.org
2011-07-03 19:01 ` jsg at openbsd dot org
2011-07-04 11:06 ` rguenth at gcc dot gnu.org
2011-07-12 13:00 ` jsg at openbsd dot org
2011-07-12 14:21 ` rguenth at gcc dot gnu.org
2011-07-12 18:04 ` mrs at gcc dot gnu.org
2011-07-28 19:25 ` jsg at openbsd dot org
2011-08-31 19:31 ` mrs at gcc dot gnu.org
2011-10-25 20:08 ` mrs at gcc dot gnu.org
2011-10-25 20:11 ` mrs at gcc dot gnu.org
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=bug-48851-4-fX3dnhfha7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).