public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50758] [4.7 Regression] Bootstrap fails at stage 2 on x86_64-apple-darwin10: error: variable 'token_no' set but not used
Date: Mon, 17 Oct 2011 15:42:00 -0000 [thread overview]
Message-ID: <bug-50758-4-xBKaA0Mh6A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50758-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50758
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-10-17 15:42:09 UTC ---
> Are you still seing this with commit r180090?
I have bootstrapped revision 180087 with the following patch
--- /opt/gcc/_clean/libcpp/line-map.c 2011-10-17 12:04:41.000000000 +0200
+++ /opt/gcc/work/libcpp/line-map.c 2011-10-17 15:36:30.000000000 +0200
@@ -625,7 +625,7 @@ source_location
linemap_macro_map_loc_to_exp_point (const struct line_map *map,
source_location location)
{
- unsigned token_no;
+ unsigned token_no __attribute__ ((__unused__));
linemap_assert (linemap_macro_expansion_map_p (map)
&& location >= MAP_START_LOCATION (map));
I guess that revision 180090 is a similar fix that should work (I'll have the
answer in a couple hours;-).
Last question: is the warning bogus or not? If no, why? If yes, I'll open a new
PR.
next prev parent reply other threads:[~2011-10-17 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:38 [Bug bootstrap/50758] New: " dominiq at lps dot ens.fr
2011-10-17 14:35 ` [Bug bootstrap/50758] " howarth at nitro dot med.uc.edu
2011-10-17 15:12 ` rguenth at gcc dot gnu.org
2011-10-17 15:27 ` dodji at seketeli dot org
2011-10-17 15:42 ` dominiq at lps dot ens.fr [this message]
2011-10-17 15:56 ` dodji at seketeli dot org
2011-10-17 19:40 ` dominiq at lps dot ens.fr
2011-10-17 19:57 ` dominiq at lps dot ens.fr
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-50758-4-xBKaA0Mh6A@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).