Welcome to Al-Manahel Newsletter List

The subscription of the email address: [EMAIL PROTECTED] To the mailing list: Al-Manahel Newsletter List is all set. Thanks for subscribing! Date of this subscription: Sun Jul 9 22:40:50 2006 Please save this email message for future reference. -

Al-Manahel Newsletter List Unsubscription

The removal of the email address: [EMAIL PROTECTED] >From the mailing list: Al-Manahel Newsletter List is all set. Date of this removal: Sun Jul 9 22:40:46 2006 Please save this email message for future reference. --

Bug#321486: Errr...

You tag this "moreinfo" yesterday, and before I have the time to provide that extra information, you close it? Can I disregard that moreinfo tag, or should I reopen the bug? -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROT

Processing of gcc-4.2_4.2-20060709-1_multi.changes

gcc-4.2_4.2-20060709-1_multi.changes uploaded successfully to localhost along with the files: gfortran-4.2_4.2-20060709-1_powerpc.deb libgcj8-dbg_4.2-20060709-1_i386.deb libstdc++6-4.2-pic_4.2-20060709-1_powerpc.deb gfortran-4.2-doc_4.2-20060709-1_all.deb lib64stdc++6-4.2-dbg_4.2

[Bug fortran/24285] format(1000(a,$))

--- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-07-09 20:49 --- (In reply to comment #4) > FX, are you working on this problem? No, I'm not working on it any more. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24285 --- You are receiving this mail because: ---

Bug#122103: probably you

Do not ignore me pleaase, I faound your email somewhere and now decided to writeb you. I am coming to your place in few weeks and thought we can meet each othber. Let me know if you do bnot mind. I am a nice pretty girl. Don't breply to this email. Email me daireclty at [EMAIL PROTECTED] --

Bug#356435: fixed in gcc-4.1 4.1.1-8

This was always known to be fixed in g++-4.1. The problem is that object files generated by g++-4.0 are compatible with each other, but can fail to link with objects generated by earlier or later versions of the compiler. So I don't see that this is fixed until g++-4.0 is removed from the archive

Bug#333733: marked as done ([fixed in 4.1] libgcj6-awt: gcj-4.0 / libgcj: Assertion error)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333733: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#375140: marked as done (gcc-4.0: s/functions call/functions that call/ gcov.1)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375140: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244496: marked as done (gnat: Illegal program not detected, ambiguous aggregate)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244496: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247573: marked as done ([fixed in 4.0] gnat: Illegal program not detected, RM 8.2(9))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247573: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#165635: marked as done ([fixed in 4.1] segmentation fault on compiling bad program)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#165635: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#276843: marked as done ([fixed in 4.1] -O2 disables warning "control reaches end of non-void function")

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#276843: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#248679: marked as done (gnat: Illegal program not detected, RM 3.4.1(5))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#248679: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#276225: marked as done (gnat: Stack overflow on illegal program, AI-306)

Your message dated Sun, 09 Jul 2006 10:47:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#276225: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#227193: marked as done ([fixed in 4.1] toplev.c: gettext interprets the two conditional strings as one)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#227193: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#66175: marked as done (gnat: GNAT miscounts UTF8 characters in string with -gnaty)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#66175: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#377012: marked as done (Having gcc-4.1 conflict, replace and provide libssp0-dev breaks cross compilers)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377012: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#349087: marked as done (g++-4.0: [ICE] segmentation fault with this 6 line long code...)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#349087: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#347601: marked as done (libstdc++6-4.0-doc: unreachable URL)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#347601: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#267788: marked as done (gnat: Bug box, Assert_Failure at atree.adb:2906 or Gigi abort, code=102 with -gnat -gnatc)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#267788: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243796: marked as done (gnat: Nonconforming parameter lists not detected)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243796: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#274942: marked as done (static libs and object files fail to link when xgot needs to be used)

Your message dated Sun, 09 Jul 2006 10:47:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#274942: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243795: marked as done (gnat: Bug box from "with Text_IO" when compiling optimized)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243795: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#248171: marked as done (gnat: Wrong output from legal program, dereferencing access all T'Class)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#248171: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#171477: marked as done (gnat: support for other debian architectures)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#171477: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243800: marked as done (gnat: Compiler crashes on illegal program (missing discriminant, unconstrained parent))

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243800: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247021: marked as done (gnat: Legal program rejected)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247021: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#276226: marked as done (gnat: Illegal program not detected, RM B.1(24))

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#276226: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243801: marked as done (gnat: Bug box at sinfo.adb:1215 on illegal program)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243801: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243799: marked as done (gnat: Compiler enters infinite loop on illegal program with tagged records)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243799: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#353366: marked as done (g++-4.0: yet another ICE (with a simple source))

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#353366: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#351786: marked as done (libstdc++6: bad thousand separator with fr_FR.UTF-8)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#351786: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244945: marked as done ([fixed in 4.0] gnat: Bug box in Gigi, code=103, on illegal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244945: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#269775: marked as done ([fixed in 4.0] gnat: Bug box in Gigi, code=116, 'Unrestricted_Access of a protected subprogram)

Your message dated Sun, 09 Jul 2006 10:47:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#269775: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#364412: marked as done (g++-4.0: problem with #pragma interface and templates turning back?)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#364412: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#251266: marked as done (gnat: Bug box, Assert_Failure at sinfo.adb:2365 on illegal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#251266: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#369547: marked as done (gfortran: strange behaviour in unformatted writing)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369547: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#374535: marked as done (gcc-4.1: FTBFS (ppc64): Please use '__powerpc64_linux_gnu__' instead of '__ppc64_linux_gnu__' in debian/multiarch.inc)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374535: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#246188: marked as done (gnat: Legal program rejected, overloaded procedures)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#246188: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#370681: marked as done (gnat: FTBFS: bashism in debian/rules)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#370681: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247016: marked as done (gnat: Legal program rejected)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247016: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244894: marked as done ([fixed in 4.1] [C++ standard defect 280] const_reverse_iterators seem to be broken)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244894: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243797: marked as done (gnat: Illegal use clause not detected)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243797: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#319309: marked as done ([fixed in 4.1, PR 22595] wrong warning: control may reach end of non-void function)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319309: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243816: marked as done (gnat: Illegal program not detected, RM 4.1.4(14))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243816: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#343692: marked as done ([m68k] ICEs while building gst-ffmpeg -- regression)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#343692: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#233208: marked as done ([fixed in 4.1] Request for stack protector enabled by default)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#213994: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247567: marked as done (gnat: Compiler enters infinite loop on illegal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247567: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#376660: marked as done ([alpha] check whether compiler driver understands Ada fails)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376660: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#248686: marked as done ([fixed in 4.0] gnat: Compiler ignores legal override of abstract subprogram)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#248686: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#228645: marked as done ([fixed in 4.1.0] call of overloaded `llabs(int)' is ambiguous)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#228645: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#335650: marked as done ([fixed in 4.1] gij: assertion failure with rhdb-explain)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335650: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#344265: marked as done ([fixed in 4.1] Segfault on -fdump-tree-all-all)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#344265: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247565: marked as done (gnat: Wrong output from legal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247565: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#322849: marked as done ("/usr/bin/ld: cannot find -laddr2line" (after "with GNAT.Traceback.Symbolic; "))

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322849: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#246388: marked as done ([fixed in 4.1] gnat: Bug box in Gigi, code=999, on legal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#246388: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#335078: marked as done (gcc-4.0: [IA-64] ICE when building keynote)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335078: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#376412: marked as done (gcc-4.0-doc: s/DegaGnu/DejaGnu/; s/incorrekt/incorrect/; gccint.html)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376412: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247563: marked as done (gnat: Legal program rejected, "limited type has no stream attributes")

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247563: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#333564: marked as done (ada,gnat: Visibility problem causes a crash instead of a warning)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333564: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247562: marked as done (gnat: Illegal program not detected, RM 3.10.2(27))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247562: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#333536: marked as done ([fixed in 4.1] [m68k] ICE in instantiate_virtual_regs_lossage)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333536: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#356435: marked as done (g++-4.0: may fail to generate all versions of inline destructor)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#356435: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#314706: marked as done (Exception in JComboBox.removeAllItems())

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314706: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244225: marked as done (gnat: Bug box in Gigi, code=116, on legal program)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244225: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#337510: marked as done ([fixed in gcj-4.1] ant code completion in eclipse generates nullpointer exception)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#337510: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#344986: marked as done (gjdoc: FTBFS on mips/mipsel: gij-wrapper-4.0 failed)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#344986: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#213994: marked as done ([fixed in 4.1] Please provide an overflow protection in the stock compiler)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#233208: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#233208: marked as done ([fixed in 4.1] Request for stack protector enabled by default)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#233208: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#263498: marked as done (gnat: Ada.Numerics.Generic_Elementary_Functions.Log erroneout with -gnatN)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#263498: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#369817: marked as done ([4.0,4.1,4.2 regression][mips] ICE in expand_expr_real_1, at expr.c:6864)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369817: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#324502: marked as done (libgcj6-awt: [GtkImage] assertion failed in compiled code)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324502: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247015: marked as done (gnat: Illegal program not detected, RM 3.9(17))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247015: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#336915: marked as done ([fixed in 4.1] Bogus warning "statement has no effect" with template and statement-expression)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#336915: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#314704: marked as done (Assertion failure when calling JTabbedPane.addTab(null, ...))

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314704: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#323016: marked as done ([m68k] while compiling tin)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323016: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#246389: marked as done (gnat: Illegal program not detected, RM 10.1.6(3))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#246389: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#369642: marked as done (g++-4.0/alpha: -fvisibility-inlines-hidden segfaults on reference to static method)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369642: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#336225: marked as done ([fixed in 4.1] g++ needs lots of RAM)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#336225: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#330279: marked as done (gcc-4.0: #pragma GCC visibility isn't properly handled for builtin functions)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330279: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#321486: marked as done ([m68k] ICE when trying to build boost)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321486: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#247014: marked as done (gnat: Illegal program not detected, RM 3.10.2(24))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#247014: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#320398: marked as done ([PR 23170] libmudflap should not use functions marked obsolescent by POSIX/SUS)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320398: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244940: marked as done ([fixed in 4.1] gnat: Bug box at sem_ch3.adb:8003)

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244940: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#342121: marked as done ([m68k] gcc-4.0 leads to segfault)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#342121: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#362840: marked as done ([fixed in 4.1] fails to compare reverse map iterators)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#362840: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#317455: marked as done ([fixed in 4.1] ICE: in cp_expr_size, at cp/cp-objcp-common.c:101)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317455: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#360906: marked as done (provide java2-runtime)

Your message dated Sun, 09 Jul 2006 10:47:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#360906: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#248677: marked as done (gnat: Cannot find generic package body, RM 1.1.3(4))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#248677: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#244483: marked as done ([fixed in 4.0] gnat: Illegal program not detected, 12.7(10) (generic parameter is visible, shouldn't be))

Your message dated Sun, 09 Jul 2006 10:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#244483: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243803: marked as done (gnat: Illegal program not detected (entry families))

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243803: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#353618: marked as done ([fixed in 4.1] [m68k] gcc-4.0 segfault building glibc)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#353618: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#355297: marked as done (Unaligned accesses with __attribute__(packed) and memcpy)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#355297: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243812: marked as done (gnat: Bug box at exp_ch9.adb:7254 on illegal code)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243812: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243807: marked as done (gnat: Illegal program not detected, RM 10.1.1(14))

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243807: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#306833: marked as done (gnat: Wrong code generated with -O -fPIC)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#306833: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#243802: marked as done (gnat: Bug box at sinfo.adb:1651 on illegal program)

Your message dated Sun, 09 Jul 2006 10:47:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#243802: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#296047: marked as done ([fixed in 4.1] gcc-3.3: grammer confusing in gcc(1): -finline-limit=n)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#296047: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#331150: marked as done ([m68k] gcc segfaults with -g -fomit-frame-pointer)

Your message dated Sun, 09 Jul 2006 10:47:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331150: fixed in gcc-4.1 4.1.1-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

  1   2   >