public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53912] [4.7/4.8 Regression] bootstrap fails using default c++ mode in stage 2 and 3 for native x86_64-w64-mingw32
Date: Fri, 20 Jul 2012 15:57:00 -0000 [thread overview]
Message-ID: <bug-53912-4-4RbDQxArYm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53912-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53912
--- Comment #16 from Uros Bizjak <ubizjak at gmail dot com> 2012-07-20 15:56:43 UTC ---
(In reply to comment #8)
> ../../../src/gcc-4.8.0/gcc/print-tree.c:258:31: error: cast from 'tree' to
> 'long unsigned int' loses precision [-fpermissive]
> hash = ((unsigned long) node) % HASH_SIZE;
>
> Same here?
Use %p with (void *) cast.
next prev parent reply other threads:[~2012-07-20 15:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 8:00 [Bug bootstrap/53912] New: bootstrap fails at stage 2 with error: cast from 'void*' to 'long int' loses precision in ggc-common.c rainer@emrich-ebersheim.de
2012-07-10 9:09 ` [Bug bootstrap/53912] [4.7 Regression] " rguenth at gcc dot gnu.org
2012-07-11 14:07 ` rainer@emrich-ebersheim.de
2012-07-16 17:10 ` [Bug bootstrap/53912] [4.7/4.8 " rainer@emrich-ebersheim.de
2012-07-16 17:17 ` rainer@emrich-ebersheim.de
2012-07-19 15:41 ` [Bug bootstrap/53912] [4.7/4.8 Regression] bootstrap fails using default c++ mode in stage 2 and 3 for native x86_64-w64-mingw32 rainer@emrich-ebersheim.de
2012-07-19 16:12 ` redi at gcc dot gnu.org
2012-07-19 20:33 ` rainer@emrich-ebersheim.de
2012-07-19 20:52 ` iant at google dot com
2012-07-19 22:31 ` rainer@emrich-ebersheim.de
2012-07-19 22:41 ` rainer@emrich-ebersheim.de
2012-07-19 23:17 ` rainer@emrich-ebersheim.de
2012-07-19 23:51 ` redi at gcc dot gnu.org
2012-07-20 15:30 ` rainer@emrich-ebersheim.de
2012-07-20 15:44 ` ubizjak at gmail dot com
2012-07-20 15:53 ` ubizjak at gmail dot com
2012-07-20 15:54 ` jakub at gcc dot gnu.org
2012-07-20 15:57 ` ubizjak at gmail dot com [this message]
2012-07-20 16:18 ` rainer@emrich-ebersheim.de
2012-08-18 13:13 ` vanboxem.ruben at gmail dot com
2012-09-07 9:43 ` rguenth at gcc dot gnu.org
2012-09-10 20:04 ` i.nixman at gmail dot com
2012-09-20 10:16 ` jakub at gcc dot gnu.org
2012-11-29 15:26 ` ktietz at gcc dot gnu.org
2012-11-29 15:28 ` ktietz at gcc dot gnu.org
2012-11-29 15:29 ` ktietz at gcc dot gnu.org
2012-11-29 18:41 ` ktietz at gcc dot gnu.org
2012-11-29 18:44 ` ktietz at gcc dot gnu.org
2012-12-03 6:56 ` ktietz at gcc dot gnu.org
2012-12-03 6:57 ` ktietz at gcc dot gnu.org
2012-12-03 7:02 ` ktietz at gcc dot gnu.org
2012-12-03 7:02 ` ktietz at gcc dot gnu.org
2012-12-03 7:05 ` ktietz at gcc dot gnu.org
2012-12-03 7:05 ` ktietz at gcc dot gnu.org
2012-12-10 9:53 ` ktietz at gcc dot gnu.org
2012-12-10 9:54 ` ktietz at gcc dot gnu.org
2012-12-10 9:57 ` ktietz at gcc dot gnu.org
2012-12-10 10:01 ` ktietz at gcc dot gnu.org
2012-12-20 19:23 ` ktietz 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-53912-4-4RbDQxArYm@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).