Bug#175478: [Bug target/9201] [3.3 regression] ICE in instantiate_virtual_regs_1 compiling octave-2.1 on m68k-linux

--- Additional Comments From gdr at gcc dot gnu dot org 2004-01-21 04:03 --- (In reply to comment #7) > This does not happen on the mainline. So, it seems to have been fixed. I'm going to close this as WONTFIX if the patch that fixed it is not obvious -- http://gcc.gnu.org/bugzill

Results for 3.4.0 20040118 (prerelease) testsuite on sparc-unknown-linux-gnu

LAST_UPDATED: Sun Jan 18 22:44:29 UTC 2004 === acats tests === FAIL: c34005a FAIL: c34005d FAIL: c34005g FAIL: c34005j FAIL: cc3601a FAIL: cxb3010 FAIL: cxb3014 FAIL: cxb3015 === acats Summary === # of expected passes1957 # of unexpected

Results for 3.4.0 20040118 (prerelease) testsuite on hppa-unknown-linux-gnu

LAST_UPDATED: Sun Jan 18 22:44:29 UTC 2004 Native configuration is hppa-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.old-deja/g++.eh/cleanup2.C (test for excess errors) WARNING: g++.old-deja/g++.eh/cleanup2.C compilation failed to produce executable FAIL: g+

Results for 3.4.0 20040118 (prerelease) testsuite on s390-ibm-linux-gnu

LAST_UPDATED: Sun Jan 18 22:44:29 UTC 2004 === acats tests === FAIL: ad8011a FAIL: c34005a FAIL: c34005d FAIL: c34005g FAIL: c34005j FAIL: c37213f FAIL: c37215f FAIL: cc3601a FAIL: cxb3010 FAIL: cxb3014 FAIL: cxb3015 === acats Summary === # of

Results for 3.4.0 20040118 (prerelease) testsuite on powerpc-unknown-linux-gnu

LAST_UPDATED: Sun Jan 18 22:44:29 UTC 2004 === acats tests === FAIL: c34005a FAIL: c34005d FAIL: c34005g FAIL: c34005j FAIL: c37213f FAIL: c37215f FAIL: cxb3010 FAIL: cxb3014 FAIL: cxb3015 === acats Summary === # of expected passes1956

Re: Bug#228506: marked as done (gcc-3.3: initalizing to zero equals uninitialised)

On Mon, Jan 19, 2004 at 07:33:10AM -0800, Debian Bug Tracking System wrote: > Further reading leads me to realise that the .bss-section is supposed to > be zero-initialized. I've always thought of .bss as a non-initialized > section (and that's how it's documentented in numerous places). Any such

Re: Include problem

Modern C++ requires namespaces... Either put "using namespace std;" right after the #include statement, or else make the modification noted below: #include int main(){ string aaa; ^^ This should be std::string return 0; } regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics

News on bug # 225621 (invalid assembly on m68k) against g77-3.3?

Hi all, I am just wondering if bug # 225621 (g77-3.3: sometimes generates invalid assembly code on m68k) has been noticed, since I haven't seen it mentioned anywhere on these mailing lists. Apologies if I'm being redundant. regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department W

Re: gcc internal compiler error on mips with octave-forge

On Tue, Jan 20, 2004 at 07:16:54PM +, Martin Michlmayr wrote: > * Dirk Eddelbuettel <[EMAIL PROTECTED]> [2004-01-20 11:06]: > > mkoctfile -DHAVE_OCTAVE_21 -v lp.cc > > /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52 > > -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTAVE_21 lp.cc -o lp.o >

Re: gcc internal compiler error on mips with octave-forge

* Dirk Eddelbuettel <[EMAIL PROTECTED]> [2004-01-20 11:06]: > mkoctfile -DHAVE_OCTAVE_21 -v lp.cc > /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52 > -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTAVE_21 lp.cc -o lp.o > lp.cc: In function ctave_value_list Flp(const octave_value_list&, int)':

gcc internal compiler error on mips with octave-forge

See http://buildd.debian.org/fetch.php?&pkg=octave-forge&ver=2004.01.18-1&arch=mips&stamp=1074506653&file=log&as=raw for more details, the pertinent part is mkoctfile -DHAVE_OCTAVE_21 -v lp.cc /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52 -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTA

[Bug bootstrap/13722] [3.4/3.5 regression] [ia64] Ada bootstrap failure

--- Additional Comments From schwab at suse dot de 2004-01-20 14:12 --- Created an attachment (id=5535) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=5535&action=view) Debugging dumps -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722 --- You are receiving this mail beca

Include problem

Submitter-Id:net Originator: Organization:Warsaw Uniwersity Confidential:no Synopsis:Include problem Severity:serious Priority:medium Category: c++ Class:rejects-legal Release:3.3.2 (Debian) (Debian testing/unstable) Enviroment: System Linux kasandra 2.4.20-wolk4.9

Include problem

Submitter-Id:net Originator: Organization:Warsaw Uniwersity Confidential:no Synopsis:Include problem Severity:serious Priority:medium Category:c++ Class:rejects-legal Release:3.3.2 (Debian) (Debian testing/unstable) Enviroment: System Linux kasandra 2.4.20-wolk4

c++ STL namespaces, which file is included?

Synopsis: STL namespaces, which file is included? Severity: serious Priority: medium Category: c++ c Class: rejects-legal Release: 3.3.2 (Debian) (Debian testing/unstable) Environment: System: Linux kasandra 2.4.20-wolk4.9s #1 Thu Sep 11 14:48:11 CEST 2003 i686 GNU/Linux Architecture: i686 host:

Bug#228645: libstdc++5-3.3-dev: call of overloaded `llabs(int)' is ambiguous

On Tue, Jan 20, 2004 at 07:05:24AM +0100, Matthias Klose wrote: > > --- > > #include > > #include > > > > using namespace std; > > > > int foo() { return llabs(1); } > > --- > > > > g++-3.3 blah.cc -c > > blah.cc: In function `int foo()': > > blah.cc:6: error: call of overloaded `llabs(int)' i

Bug#228645: libstdc++5-3.3-dev: call of overloaded `llabs(int)' is ambiguous

Glenn Maynard writes: > --- > #include > #include > > using namespace std; > > int foo() { return llabs(1); } > --- > > g++-3.3 blah.cc -c > blah.cc: In function `int foo()': > blah.cc:6: error: call of overloaded `llabs(int)' is ambiguous > /usr/include/stdlib.h:754: error: candidates are: lo