[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-10 05:09 --- Can you try it again as it sounds like the patch which I applied: should fix this problem? -- What|Removed |Ad

[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-03-10 05:07 --- Subject: Bug 12371 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2004-03-10 05:07:46 Modified files: gcc: ChangeLog gcc/config/m68k: m

[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-03-10 05:07 --- Subject: Bug 12371 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-3_4-branch Changes by: [EMAIL PROTECTED] 2004-03-10 05:07:15 Modified files: gcc: Change

[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-10 04:49 --- Roman I will apply your patch to both the mainline and 3.4.0. -- What|Removed |Added

[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From mark at codesourcery dot com 2004-03-10 04:47 --- Subject: Re: [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-10 > 04:42 -

[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-10 04:42 --- Mark there is a patch here to fix it: . -- What|Removed |Added

[Bug libstdc++/14493] No std::bad_alloc::what() const

--- Additional Comments From giovannibajo at libero dot it 2004-03-10 01:12 --- (In reply to comment #10) > Honestly, is "std::bad_alloc" really that much more readable than > "St9bad_alloc"? Especially compared to "bad allocation"? Well, "St9bad_alloc" looks like memory corruption, u

Results for 3.4.0 20040215 (prerelease) testsuite on mipsel-unknown-linux-gnu

LAST_UPDATED: Sun Feb 15 16:20:48 UTC 2004 === acats tests === FAIL: c34005a FAIL: c34005d FAIL: c34005g FAIL: c34005j FAIL: c37213f FAIL: c37215f FAIL: cc3601a FAIL: cxb3010 FAIL: cxb3014 FAIL: cxb3015 === acats Summary === # of expected passes

Generic meds form Canada!

Save Money, Buy GENERIC! Prescription drugs with NO prior prescription needed! - XANAX - (to treat anxiety) - PHENTERMINE - (for weight loss) - Viagra - (got wood?) - Ambian - (For a Great Night’s Sleep) - Lipitor - (to reduce cholesterol) - NEXIUM - (to treat acid reflux and GERD) - PAXIL

gcc-2.95_2.95.4.ds15-21_i386.changes ACCEPTED

Accepted: chill-2.95_2.95.4-21_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-21_i386.deb cpp-2.95-doc_2.95.4-21_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-21_all.deb cpp-2.95_2.95.4-21_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-21_i386.deb g++-2.95_2.95.4-21_i386.deb to

Bug#237126: [arm] ICE when compiling nessus 2.0.10a

Package: gcc-3.3 Version: 1:3.3.3-0pre3 Priority: normal When compiling nessus 2.0.10a in the arm architecture: (...) cc -g -Wall -O2 `sh ./cflags` -c monitor_dialog.c gcc -g -Wall -O2 `sh ./cflags` -c backend.c backend.c: In function `backend_empty': backend.c:566: error: insn does not

gcc-2.95_2.95.4.ds15-21_m68k.changes ACCEPTED

Accepted: chill-2.95_2.95.4-21_m68k.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-21_m68k.deb cpp-2.95_2.95.4-21_m68k.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-21_m68k.deb g++-2.95_2.95.4-21_m68k.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-21_m68k.deb g77-2.95_2.95.4-21_m68k.deb to pool/

Processing of gcc-2.95_2.95.4.ds15-21_i386.changes

gcc-2.95_2.95.4.ds15-21_i386.changes uploaded successfully to localhost along with the files: gcc-2.95_2.95.4.ds15-21.dsc gcc-2.95_2.95.4.ds15.orig.tar.gz gcc-2.95_2.95.4.ds15-21.diff.gz cpp-2.95-doc_2.95.4-21_all.deb g77-2.95-doc_2.95.4-21_all.deb gcc-2.95-doc_2.95.4-21_all.deb gpc-2

Processing of gcc-2.95_2.95.4.ds15-21_m68k.changes

gcc-2.95_2.95.4.ds15-21_m68k.changes uploaded successfully to localhost along with the files: gcc-2.95_2.95.4-21_m68k.deb cpp-2.95_2.95.4-21_m68k.deb g++-2.95_2.95.4-21_m68k.deb gobjc-2.95_2.95.4-21_m68k.deb g77-2.95_2.95.4-21_m68k.deb chill-2.95_2.95.4-21_m68k.deb libstdc++2.10-glibc

[Bug libstdc++/14493] No std::bad_alloc::what() const

--- Additional Comments From zack at codesourcery dot com 2004-03-09 20:14 --- Subject: Re: No std::bad_alloc::what() const "pme at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: >> It appears to me that the original reporter wanted what() to return >> an "intelligible error message"

[Bug libstdc++/14493] No std::bad_alloc::what() const

--- Additional Comments From pme at gcc dot gnu dot org 2004-03-09 19:48 --- (In reply to comment #5) > It appears to me that the original reporter wanted what() to return > an "intelligible error message" a la icc's "bad allocation", rather > than "St9bad_alloc" (which does communicate

Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

On Tue, Mar 09, 2004 at 07:32:32PM +0100, Jeroen T. Vermeulen wrote: > On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > > > More to the point, it doesn't matter how it's implemented, and the user > > > should not care. It only matters that > > > > > > std::bad_alloc foo; >

[Bug libstdc++/14493] No std::bad_alloc::what() const

--- Additional Comments From phil at jaj dot com 2004-03-09 19:32 --- Subject: Re: Bug#236912: No std::bad_alloc::what() const On Tue, Mar 09, 2004 at 07:32:32PM +0100, Jeroen T. Vermeulen wrote: > On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > > > More to the poin

Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > More to the point, it doesn't matter how it's implemented, and the user > > should not care. It only matters that > > > > std::bad_alloc foo; > > std::cerr << foo.what() << std::endl; > > > > works, which the submitter

[Bug libstdc++/14493] No std::bad_alloc::what() const

--- Additional Comments From jtv at xs4all dot nl 2004-03-09 18:32 --- Subject: Re: No std::bad_alloc::what() const On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > More to the point, it doesn't matter how it's implemented, and the user > > should not care. It only

Bug#237029: gcc-snapshot: cannot prelink several java-related binaries

Package: gcc-snapshot Version: 20040215-1 Severity: normal Hi, I suppose that gcc-snapshot is currently superseded by gcc-3.4-pre in experimental, but this report may be useful once you package gcc 3.5 in gcc-snapshot (hint!, hint! :>). Anyway here is what prelink complains about: /usr/sbin/pr

Bug#237023: gcc-3.2: Uninstall of gcc-3.2 attempts to install old python, tcl packages

Package: gcc-3.2 Version: 1:3.2.3-2 Severity: normal Tags: sid I tried to uninstall gcc-3.2, but the package insists that it must install old versions of python and other packages in order to uninstall. Example: tmp# apt-get -s remove gcc-3.2 Reading Package Lists... Done Building Dependency Tree

[Bug c++/14242] [3.4/3.5 regression] symbol lookup in templates

--- Additional Comments From mmitchel at gcc dot gnu dot org 2004-03-09 07:02 --- This is not a bug. The name is non-dependent, and so name lookup finds only the first two declarations. -- What|Removed |Added --