with !(==)
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: peter_foelsche at agilent dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40561
--- Comment #1 from peter_foelsche at agilent dot com 2009-06-26 17:29
---
Created an attachment (id=18074)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18074&action=view)
gpperror.cpp
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40561
--- Comment #2 from peter_foelsche at agilent dot com 2009-06-26 17:36
---
Created an attachment (id=18075)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18075&action=view)
gpperror.cpp
--
peter_foelsche at agilent dot com changed:
What|
Summary: compiler gives up optimizing even on 64bit systems
Product: gcc
Version: 4.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pe
--- Comment #1 from peter_foelsche at agilent dot com 2008-09-19 20:39
---
sorry -- I did discover the matching option to increase memory.
--
peter_foelsche at agilent dot com changed:
What|Removed |Added
--- Comment #4 from peter_foelsche at agilent dot com 2009-08-26 18:06
---
Created an attachment (id=18430)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18430&action=view)
gpperror.cpp
shorter testcase
--
peter_foelsche at agilent dot com changed:
--- Comment #5 from peter_foelsche at agilent dot com 2009-08-26 18:13
---
seems to be fixed in gcc v4.4.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40561
ority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: peter_foelsche at agilent dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #1 from peter_foelsche at agilent dot com 2009-12-12 01:34
---
Created an attachment (id=19280)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19280&action=view)
console output of the compiler
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #2 from peter_foelsche at agilent dot com 2009-12-12 01:36
---
maybe on Monday I can create an instance like described of the offending
classes
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #3 from peter_foelsche at agilent dot com 2009-12-12 01:37
---
the compiler takes more than 10GB of RAM.
There is 40GB of RAM available.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #4 from peter_foelsche at agilent dot com 2009-12-12 01:40
---
the same happens with boost 1_40
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #6 from peter_foelsche at agilent dot com 2009-12-15 20:58
---
Created an attachment (id=19313)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19313&action=view)
tmp.cpp
g++ -c tmp.cpp -I ~/boost_1_40_0 -g
-g is important
--
http://gcc.gnu.org/b
--- Comment #9 from peter_foelsche at agilent dot com 2010-01-04 18:12
---
Created an attachment (id=19464)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19464&action=view)
tmp.ii
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
--- Comment #12 from peter_foelsche at agilent dot com 2010-01-04 20:00
---
(In reply to comment #10)
> Please also provide output of g++ -v. If you manage to compile this
> successfully then the output of -ftime-report will also be interesting.
> Confirmed with -g (-g0 is
--- Comment #13 from peter_foelsche at agilent dot com 2010-01-08 21:37
---
boost::mpl::sort seems to be known to be a memory hog.
Also on other platforms.
I replaced this with other code.
--
peter_foelsche at agilent dot com changed:
What|Removed
orary
object
Product: gcc
Version: 4.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: peter_foelsche at agilent dot com
http://gcc.gnu.org/bug
--- Comment #1 from peter_foelsche at agilent dot com 2007-11-16 16:38
---
Created an attachment (id=14564)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14564&action=view)
test.cpp
contains a main function at the end which calls printf() with some temporary
objects
--- Comment #2 from peter_foelsche at agilent dot com 2007-11-16 16:42
---
the attached piece of source code does exhibit the compiler problem with the
new compiler.
When compiling using -O3 the code works fine. When compiling using -g the bug
happens.
Some temporary objects are being
--- Comment #3 from peter_foelsche at agilent dot com 2007-11-16 16:45
---
We tested this only for the 64bit version.
I don't know if this happens for the 32bit version.
The operating system is LINUX:
Linux bonfire 2.4.21-47.0.1.EL #1 SMP Fri Oct 13 17:51:36 EDT 2006 x86_64
x
20 matches
Mail list logo
