[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-29 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-29 22:14 --- Fixed with: 2005-08-29 Paolo Carlini <[EMAIL PROTECTED]> PR libstdc++/23528 Port from HEAD/4_0-branch: 2004-07-28 Matt Austern <[EMAIL PROTECTED]> * include/ext/hashtable.h: Us

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 18:23 --- (In reply to comment #11) Thanks a lot. I think adding a proper rebind is the right way to fix the problem, already used in mainline and 4_0-branch, by the way. -- What|Removed

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread mattias dot ellert at tsl dot uu dot se
--- Additional Comments From mattias dot ellert at tsl dot uu dot se 2005-08-23 17:14 --- (In reply to comment #10) Your proposed alternative patch works for me. Both for the testcase in this bug report and when I compile the code I was building when I found the bug. -- http://gcc.g

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 13:55 --- It looks like the problem has been fixed in revision 1.6 of hashtable.h. Mattias, can you experiment a bit with just changing in class hashtable: typedef _Alloc allocator_type; to typedef typename _Alloc::t

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-23 13:42 --- Oh and the preprocessed created with 3.4.0 gives the same error on the mainline too. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23528

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 13:42 --- (In reply to comment #7) > A big mistery... Actually, in 3_4-branch memory allocation in class hashtable was rather different, forgot about that. The bug is there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 13:34 --- (In reply to comment #6) Ok, Andrew is right, just double checked. A big mistery... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23528

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 13:26 --- (In reply to comment #5) I find this very hard to believe: the ext/ headers are basically frozen. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23528

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-23 13:18 --- I forgot to mention that the preprocessed source from 4.1.0 compiles just fine with the 3.4.0 compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23528

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-08-23 13:15 --- I agree that something much more subtle is going on, maybe even a C++ front-end bug in 3_4-branch. Notice that hash_map<>::allocator_type is typedef-ed as _Ht::allocator_type, which, in turn (see the hashtable clas

[Bug libstdc++/23528] [3.4 Regression] Wrong default allocator in ext/hash_map

2005-08-23 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-23 12:42 --- This works in both on the mainlline and in 4.0.0. Also the fix is not really a correct fix as this area was not what changed between 3.4.0 and 4.0.0. -- What|Removed |