--- Comment #4 from pinskia at gcc dot gnu dot org 2006-03-20 07:57 ---
I could not reduce this to a good point (at least today).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26757
--- You are receiving this mail because: ---
You reported the bug, or are watching the
On Sun, Mar 19, 2006 at 11:13:13PM +, Martin Michlmayr wrote:
severity 356896 important
I would have thought that a compiler that miscompiles trivial for loops and
thus inserts bugs in lots of programs compiled with it is unsuitable for
release, i.e. severity serious.
Do you have a test
--- Comment #1 from rguenth at gcc dot gnu dot org 2006-03-20 10:15 ---
Confirmed. -fno-tree-loop-optimize makes it work.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
CC||rguenth at gcc dot gnu dot
|
* Martin Buck [EMAIL PROTECTED] [2006-03-20 10:03]:
I would have thought that a compiler that miscompiles trivial for loops and
thus inserts bugs in lots of programs compiled with it is unsuitable for
release, i.e. severity serious.
I don't know... I compiled 5000 packages and none showed a
Processing commands for [EMAIL PROTECTED]:
forwarded 356569 http://gcc.gnu.org/PR26757
Bug#356569: ICE on 4.1 that doesn't happen with 4.0 (3ddesktop_0.2.9-5.1)
Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR26757.
--
Stopping processing here.
Please contact me if
--
halcy0n at gentoo dot org changed:
What|Removed |Added
CC||toolchain at gentoo dot org
Package: g++-4.0
Version: 4.0.3-1
Severity: normal
g++ compiles the following wrong C++ code without complaining:
#include complex
class A {
public:
A() {}
};
int main()
{
std::complexdouble bla(bla);
A blubb(blubb);
}
This bug also affects g++-3.4.
Michael Weitzel [EMAIL PROTECTED] writes:
Package: g++-4.0
Version: 4.0.3-1
Severity: normal
g++ compiles the following wrong C++ code without complaining:
#include complex
class A {
public:
A() {}
};
int main()
{
std::complexdouble bla(bla);
A
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#340965: gij-4.1 memory leak with JAP,
which was filed against the gij-4.1 package.
It has been closed by one of the developers, namely
Matthias Klose [EMAIL PROTECTED].
Their explanation is
Philipp Klaus Krause writes:
Version: 4.1.0-0
What do you mean by Version: 4.1.0-0 as a reason for closing the bug?
I see the bug with that version, too.
I didn't see that memory leak in this version. If it's still there,
please add instructions how to see/measure it.
Matthias
--
To
Matthias Klose wrote:
Philipp Klaus Krause writes:
Version: 4.1.0-0
What do you mean by Version: 4.1.0-0 as a reason for closing the bug?
I see the bug with that version, too.
I didn't see that memory leak in this version. If it's still there,
please add instructions how to see/measure it.
* Martin Michlmayr [EMAIL PROTECTED] [2006-03-20 23:10]:
Falk, even without a minimal test case, do you think you can forward
this upstream. Maybe someone there'll have a good idea. I can also
produce pregenerated code for xbsql (the package that fails in
#356245) if you want.
Oh, and
* Ben Hutchings [EMAIL PROTECTED] [2006-03-12 01:41]:
Where a base class has a destructor defined inline, g++ may generate
code for a derived class's destructor that calls an non-inline version
of the base class destructor, but without generating code for the
latter. This is normally masked
Package: g++-4.1
Version: 4.1.0-0
Severity: minor
The line number mentioned in the extra qualification error is not
ideal. Instead of showing the line number on which the extra
qualification actually occurs, or should the last line of the
declaration.
(sid)6102:[EMAIL PROTECTED]: ~] cat
LAST_UPDATED:
Native configuration is arm-unknown-linux-gnu
=== libstdc++-v3 tests ===
Running target unix
XPASS: 22_locale/collate_byname.cc execution test
XPASS: 22_locale/collate_members_char.cc execution test
XPASS: 22_locale/collate_members_wchar_t.cc execution test
XPASS:
LAST_UPDATED: Obtained from SVN: tags/gcc_4_1_0_release revision 111560
=== acats tests ===
=== acats Summary ===
# of expected passes2316
# of unexpected failures0
Native configuration is sparc-unknown-linux-gnu
=== g++ tests
LAST_UPDATED:
Native configuration is s390-ibm-linux-gnu
=== g++ tests ===
Running target unix
XPASS: g++.brendan/union1.C (test for excess errors)
XPASS: g++.oliva/linkage1.C (test for excess errors)
XPASS: g++.other/init5.C Execution test
FAIL: g++.pt/repo3.C (test for
Package: g++-4.0
Version: 4.0.3-1
Severity: grave
Justification: renders package unusable
g++ (or cpp, for that matter) is not able to find the standard C++
headers and terminates with (example: typeinfo) ``error: typeinfo:
No such file or directory'' although /usr/include/c++/4.0.3/typeinfo
severity 358076 normal
tags 358076 unreproducible
thanks
On Tue, Mar 21, 2006 at 04:29:14AM +0100, Christian E. Boehme wrote:
g++ (or cpp, for that matter) is not able to find the standard C++
headers and terminates with (example: typeinfo) ``error: typeinfo:
No such file or directory''
Processing commands for [EMAIL PROTECTED]:
severity 358076 normal
Bug#358076: g++-4.0: fails to locate std C++ headers (eg, typeinfo)
Severity set to `normal'.
tags 358076 unreproducible
Bug#358076: g++-4.0: fails to locate std C++ headers (eg, typeinfo)
There were no tags set.
Tags added:
21 matches
Mail list logo
