https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #13 from rguenther at suse dot de rguenther at suse dot de ---
On Wed, 20 May 2015, jakub at gcc dot gnu.org wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
Jakub Jelinek jakub at gcc dot gnu.org changed:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||jakub at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #15 from Douglas Mencken dougmencken at gmail dot com ---
I'm going to surround calls to gcc_[checking_]assert (in gcc/hash-table.*) with
#ifdef ENABLE_CHECKING {--disable-checking is in my config already}. Let's see
where it lands.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #17 from rguenther at suse dot de rguenther at suse dot de ---
On Wed, 20 May 2015, dougmencken at gmail dot com wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #14 from Douglas Mencken dougmencken at gmail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #14 from Douglas Mencken dougmencken at gmail dot com ---
sizeof(hashval_t) = 4, CHAR_BIT = 8
Just checked it manually. Built with patch subset, genmatch problem is here
again. It isn't related to changes in hash_table_mod1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #16 from Andreas Schwab sch...@linux-m68k.org ---
After, = 32 triggers assert (-- failure).
This is backwards. The failure case is sizeof (hashval_t) * CHAR_BIT 32.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #18 from Douglas Mencken dougmencken at gmail dot com ---
try without --disable-checking
Okay, doing it now.
Meanwhile. Why ``sizeof (hashval_t) * CHAR_BIT'' cannot be checked at configure
time, not at buildtime nor runtime?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #19 from Jakub Jelinek jakub at gcc dot gnu.org ---
(In reply to Douglas Mencken from comment #18)
try without --disable-checking
Okay, doing it now.
Meanwhile. Why ``sizeof (hashval_t) * CHAR_BIT'' cannot be checked at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #20 from Douglas Mencken dougmencken at gmail dot com ---
I'm lost. “Vanilla” 5.1.0 configured without --disable-checking went thru
stage2 w/o any issue...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #10 from Douglas Mencken dougmencken at gmail dot com ---
No, ``ld warning: atom sorting error'' has nothing to do with this issue.
For example, commit 2e723940b6a1e61dfb20e03b30fba89dd204b72d (2014-12-19),
genmatch@stage2 works fine
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #11 from Douglas Mencken dougmencken at gmail dot com ---
Causing commit found.
It is r218976 (e2afa5c10fd41fe708959121f373fcb5435ef5d6). With reverse-applied
r218976's patch, 5.1.0 even reaches Bootstrap comparison failure!‘‘ ;)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #9 from Douglas Mencken dougmencken at gmail dot com ---
I decided to use git bisect to figure out.
Working genmatch@stage2:
commit 852fa94e29ebd44814054f4657b7385788b0321b (2014-12-16)
$ prev-gcc/build/genmatch --gimple
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #8 from Douglas Mencken dougmencken at gmail dot com ---
Created attachment 35546
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35546action=edit
linker output for genmatch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
--- Comment #7 from Douglas Mencken dougmencken at gmail dot com ---
$ ls -l /usr/bin/ld
-rwxr-xr-x 1 root wheel 2622416 Jul 12 2008 /usr/bin/ld
$ /usr/bin/ld -v
@(#)PROGRAM:ld PROJECT:ld64-85.2.1
LLVM version 3.5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
CC||mikestump at
15 matches
Mail list logo
