[Bug libstdc++/16611] Terrible code generated for vector

2006-08-06 Thread pcarlini at suse dot de
--- Comment #12 from pcarlini at suse dot de 2006-08-06 14:47 --- Now I get: <_Z1fRKSt6vectorIbSaIbEEj>: 0: 55 push %ebp 1: 89 e5 mov%esp,%ebp 3: 8b 45 08mov0x8(%ebp),%eax 6: 8b 4d 0c

[Bug libstdc++/16611] Terrible code generated for vector

2006-08-06 Thread paolo at gcc dot gnu dot org
--- Comment #11 from paolo at gcc dot gnu dot org 2006-08-06 14:45 --- Subject: Bug 16611 Author: paolo Date: Sun Aug 6 14:45:04 2006 New Revision: 115972 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115972 Log: 2006-08-06 Paolo Carlini <[EMAIL PROTECTED]> PR libst

[Bug libstdc++/16611] Terrible code generated for vector

2006-08-05 Thread pcarlini at suse dot de
-- pcarlini at suse dot de changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |pcarlini at suse dot de |dot org |

[Bug libstdc++/16611] Terrible code generated for vector

2005-12-23 Thread pcarlini at suse dot de
--- Comment #10 from pcarlini at suse dot de 2005-12-23 21:13 --- Well, I'm not sure that, besides code size, 4_1 is doing better than 4.0.2, but both are certainly better than 3.4.x. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16611

[Bug libstdc++/16611] Terrible code generated for vector

2005-12-23 Thread pcarlini at suse dot de
--- Comment #9 from pcarlini at suse dot de 2005-12-23 20:12 --- FWIW, on x86-linux at least, we are making progress on the compiler side. With 4.0.2 I get (-O2): <_Z1fRKSt6vectorIbSaIbEEj>: 0: 55 push %ebp 1: 89 e5 mov%es

[Bug libstdc++/16611] Terrible code generated for vector

2005-04-18 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-04-18 14:23 --- > This is news to me. Does this mean that vector is not going to be > special- > cased any more? That seems like a very bad idea to me, since programs will > suddenly take 8 times as much memory (or even more). Wh

[Bug libstdc++/16611] Terrible code generated for vector

2005-04-18 Thread falk at debian dot org
--- Additional Comments From falk at debian dot org 2005-04-18 08:10 --- (In reply to comment #6) > Hi. It can well be a libstdc++ problem, and indeed I can imagine ways to avoid > signed integers in the code. However, I'm not sure that someone will actually > do the work, given the soon

[Bug libstdc++/16611] Terrible code generated for vector

2005-04-17 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-04-17 16:34 --- Hi. It can well be a libstdc++ problem, and indeed I can imagine ways to avoid signed integers in the code. However, I'm not sure that someone will actually do the work, given the soon-to-be-deprecated status of ve

[Bug libstdc++/16611] Terrible code generated for vector

2005-04-12 Thread sabre at nondot dot org
--- Additional Comments From sabre at nondot dot org 2005-04-12 14:31 --- This is definately a libstdc++ issue. -Chris -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16611

[Bug libstdc++/16611] Terrible code generated for vector

2005-04-12 Thread falk at debian dot org
--- Additional Comments From falk at debian dot org 2005-04-12 08:07 --- (In reply to comment #3) > This code from stl_bvector.h is the problem: [...] Hmm, right. I don't fully understand why it is done in this complicated manner, does vector::operator[] need to do anything more than my