Results for 3.2.3 20030221 (Debian prerelease) testsuite on i386-pc-netbsdelf-gnu

LAST_UPDATED: Fri Feb 21 16:24:42 UTC 2003 Native configuration is i386-pc-netbsdelf-gnu === g++ tests === Running target unix === g++ Summary === # of expected passes7360 # of expected failures 89 # of untested testcases 15 # of un

Results for 3.2.3 20030221 (Debian prerelease) testsuite on hppa-unknown-linux-gnu

LAST_UPDATED: Fri Feb 21 16:24:42 UTC 2003 Native configuration is hppa-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.mike/eh33.C (test for excess errors) XPASS: g++.mike/eh33.C Execution test XPASS: g++.mike/eh50.C (test for excess errors) XPASS: g++.mike/

Results for 3.3 20030222 (prerelease) testsuite on ia64-unknown-linux-gnu

LAST_UPDATED: Sat Feb 22 05:29:16 UTC 2003 Native configuration is ia64-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/warn/Wunused-2.C (test for warnings, line 5) FAIL: g++.dg/tls/init-2.C (test for excess errors) XPASS: g++.other/init5.C Execution test

gcc-snapshot_20030221-1_m68k.changes ACCEPTED

Accepted: gcc-snapshot_20030221-1_m68k.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20030221-1_m68k.deb Thank you for your contribution to Debian.

Re: GNAT 3.15p

Florian Weimer <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Jérôme Marant) writes: > >> Nonetheless, I suspect that the package won't build on sparc, >> since 5smastop.adb at least has disappeared in this version. >> Sam ported GNAT to sparc/linux and powerpc/linux and I have no >> idea about

Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

On Mon, Feb 24, 2003 at 12:28:44AM -0800, Alexander Hvostov wrote: > As noted in the corresponding man page, the 'sprintf' and 'vsprintf' > functions are > insecure, and should not be used. I suggest that gcc print a warning when > compiling > code in which they are used, as it already does with

Bug#180486: gcc-3.2: miscompilation on powerpc with -O2 or higher

On Mon, Feb 24, 2003 at 10:14:03AM -0500, Camm Maguire wrote: > Greetings! > > Matthias Klose <[EMAIL PROTECTED]> writes: > > > Camm Maguire writes: > > > Package: gcc-3.2 > > > Version: 1:3.2.2-1 > > > Severity: normal > > > > > > When compiling GCL, the produced lisp image segfaults early on >

Bug#180486: gcc-3.2: miscompilation on powerpc with -O2 or higher

Greetings! Matthias Klose <[EMAIL PROTECTED]> writes: > Camm Maguire writes: > > Package: gcc-3.2 > > Version: 1:3.2.2-1 > > Severity: normal > > > > When compiling GCL, the produced lisp image segfaults early on > > iwhen using -O2 or higher. All is fine with -O, or with full > > optimization

Processed: Re: Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

Processing commands for [EMAIL PROTECTED]: > tags 182277 - security Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf. Tags were: security Tags removed: security > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

tags 182277 - security thanks On Mon, Feb 24, 2003 at 12:28:44AM -0800, Alexander Hvostov wrote: > Package: gcc-3.2 > Version: 1:3.2.3-0pre1 > Severity: normal > Tags: security > > As noted in the corresponding man page, the 'sprintf' and 'vsprintf' > functions are > insecure, and should not be

Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

Package: gcc-3.2 Version: 1:3.2.3-0pre1 Severity: normal Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As noted in the corresponding man page, the 'sprintf' and 'vsprintf' functions are insecure, and should not be used. I suggest that gcc print a warning when compiling code in wh