public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rainer@emrich-ebersheim.de" <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: Thu, 19 Jul 2012 20:33:00 -0000	[thread overview]
Message-ID: <bug-53912-4-OdXl7TvdyH@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 #6 from Rainer Emrich <rainer@emrich-ebersheim.de> 2012-07-19 20:33:01 UTC ---
Am 19.07.2012 18:12, schrieb redi at gcc dot gnu.org:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53912
> 
> --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-19 16:12:18 UTC ---
> Does changing the definition of POINTER_HASH to use intptr_t instead of long
> work?
> 
This works for ggc-common.c. Ian Lance Taylor recommended to use uintptr_t
instead, but I haven't tested that.

The next failure now is:
/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/./prev-gcc/g++
-B/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/./prev-gcc/
-B/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-4.8.0/x86_64-w64-mingw32/bin/
-nostdinc++
-B/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/src/.libs
-B/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/libsupc++/.libs
-I/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/include/x86_64-w64-mingw32
-I/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/include
-I/SCRATCH/tmp.xipisatGtI/src/gcc-4.8.0/libstdc++-v3/libsupc++
-L/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/src/.libs
-L/SCRATCH/tmp.xipisatGtI/gcc-4.8.0/gcc-4.8.0/prev-x86_64-w64-mingw32/libstdc++-v3/libsupc++/.libs
-c   -g -O2 -D__USE_MINGW_ACCESS -Wno-pedantic-ms-format -gtoggle -DIN_GCC
-fno-exceptions -fno-rtti -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings   -DHAVE_CONFIG_H -I. -I. -I../../../src/gcc-4.8.0/gcc
-I../../../src/gcc-4.8.0/gcc/. -I../../../src/gcc-4.8.0/gcc/../include
-I./../intl -I../../../src/gcc-4.8.0/gcc/../libcpp/include
-I/SCRATCH/tmp.xipisatGtI/install/include
-I/SCRATCH/tmp.xipisatGtI/install/include
-I/SCRATCH/tmp.xipisatGtI/install/include
-I../../../src/gcc-4.8.0/gcc/../libdecnumber
-I../../../src/gcc-4.8.0/gcc/../libdecnumber/bid -I../libdecnumber
-DCLOOG_INT_GMP -I/SCRATCH/tmp.xipisatGtI/install/include
-I/SCRATCH/tmp.xipisatGtI/install/include
../../../src/gcc-4.8.0/gcc/pointer-set.c -o pointer-set.o
../../../src/gcc-4.8.0/gcc/pointer-set.c: In function 'size_t hash1(const
void*,
long unsigned int, long unsigned int)':
../../../src/gcc-4.8.0/gcc/pointer-set.c:67:32: error: cast from 'const void*'
to 'long unsigned int' loses precision [-fpermissive]
   return ((A * (unsigned long) p) >> shift) & (max - 1);
                                ^
make[3]: *** [pointer-set.o] Error 1


  parent reply	other threads:[~2012-07-19 20:33 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 [this message]
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
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-OdXl7TvdyH@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).