[Bug c++/26757] C++ front-end producing two DECLs with the same UID

--- Comment #28 from jakub at gcc dot gnu dot org 2006-06-13 09:21 --- Subject: Bug 26757 Author: jakub Date: Tue Jun 13 09:21:30 2006 New Revision: 114607 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114607 Log: PR middle-end/27793 * cp-tree.h (cxx_int_tree_ma

Bug#117765: my destiny

Hi there lovely, This kind of opportunity comes ones in a life. bI don't waant to miss it. Do you? I am coming to your place ibn few days and I though may be we can cmeet each other. If you don't mind I can sendb you my picture. I am a girl.c You can correspond with me using my email [EMAIL PROTE

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: Tue Jun 13 06:39:40 2006 Please save this email message for future reference. --

Processing of gcc-4.1_4.1.1-4_multi.changes

gcc-4.1_4.1.1-4_multi.changes uploaded successfully to localhost along with the files: lib64ssp0_4.1.1-4_i386.deb gcc-4.1_4.1.1-4.diff.gz libstdc++6_4.1.1-4_powerpc.deb gcc-4.1_4.1.1-4_powerpc.deb libssp0-dev_4.1.1-4_i386.deb libgnatvsn4.1_4.1.1-4_powerpc.deb protoize_4.1.1-4_powerpc.

gcc-4.1_4.1.1-4_multi.changes ACCEPTED

Accepted: cpp-4.1-doc_4.1.1-4_all.deb to pool/main/g/gcc-4.1/cpp-4.1-doc_4.1.1-4_all.deb cpp-4.1_4.1.1-4_i386.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-4_i386.deb cpp-4.1_4.1.1-4_powerpc.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-4_powerpc.deb fastjar_4.1.1-4_i386.deb to pool/main/g/gcc-4.1/f

gcc-4.1 override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): gcc-4.1-base_4.1.1-4_i386.deb: package says section is libs, override says devel. gcc-4.1-base_4.1.1-4_powerpc.deb: package says section is libs, override says devel. Either the package

Bug#372559: marked as done (gecode: FTBFS with g++-4.1: no suitable operator)

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372152: fixed in gcc-4.1 4.1.1-4 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#372152: marked as done (g++-4.1: PR27935 appears to be unresolved (operator delete(void*, size_t) issue))

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372559: fixed in gcc-4.1 4.1.1-4 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#372705: marked as done (kdelibs: FTBFS: no suitable 'operator delete')

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372559: fixed in gcc-4.1 4.1.1-4 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#372152: marked as done (g++-4.1: PR27935 appears to be unresolved (operator delete(void*, size_t) issue))

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372152: fixed in gcc-4.1 4.1.1-4 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#372559: marked as done (gecode: FTBFS with g++-4.1: no suitable operator)

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372559: fixed in gcc-4.1 4.1.1-4 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#372705: marked as done (kdelibs: FTBFS: no suitable 'operator delete')

Your message dated Tue, 13 Jun 2006 11:17:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372152: fixed in gcc-4.1 4.1.1-4 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

[bts-link] source package gcc-4.1

# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #336114 # * http://gcc.gnu.org/PR24712 # * remote status changed: UNCONFIRMED -> RESOLVED # * remote resolu

Processed: [bts-link] source package gcc-4.1

Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report f

gcc-4.1_4.1.1-4_hppa.changes ACCEPTED

Accepted: cpp-4.1_4.1.1-4_hppa.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-4_hppa.deb fastjar_4.1.1-4_hppa.deb to pool/main/g/gcc-4.1/fastjar_4.1.1-4_hppa.deb fixincludes_4.1.1-4_hppa.deb to pool/main/g/gcc-4.1/fixincludes_4.1.1-4_hppa.deb g++-4.1_4.1.1-4_hppa.deb to pool/main/g/gcc-4.1/g++-4

Processing of gcc-4.1_4.1.1-4_hppa.changes

gcc-4.1_4.1.1-4_hppa.changes uploaded successfully to localhost along with the files: gcc-4.1-base_4.1.1-4_hppa.deb libgcc4_4.1.1-4_hppa.deb cpp-4.1_4.1.1-4_hppa.deb protoize_4.1.1-4_hppa.deb fixincludes_4.1.1-4_hppa.deb libmudflap0_4.1.1-4_hppa.deb libmudflap0-dev_4.1.1-4_hppa.deb

gcc-snapshot_20060613-1_multi.changes ACCEPTED

Accepted: gcc-snapshot_20060613-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20060613-1.dsc gcc-snapshot_20060613-1.tar.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20060613-1.tar.gz gcc-snapshot_20060613-1_i386.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20060613-1_i386.deb gcc-snapshot_2

Processing of gcc-snapshot_20060613-1_multi.changes

gcc-snapshot_20060613-1_multi.changes uploaded successfully to localhost along with the files: gcc-snapshot_20060613-1_powerpc.deb gcc-snapshot_20060613-1.tar.gz gcc-snapshot_20060613-1_i386.deb gcc-snapshot_20060613-1.dsc Greetings, Your Debian queue daemon -- To UNSUBSCRIBE,

Bug#369606: marked as done (ICE: verify_stmts failed)

Your message dated Tue, 13 Jun 2006 17:32:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369606: fixed in gcc-snapshot 20060613-1 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 c

Bug#361883: marked as done (Incorrect integer division (wrong sign))

Your message dated Tue, 13 Jun 2006 17:32:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#361883: fixed in gcc-snapshot 20060613-1 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 c

Bug#369810: marked as done (FTBFS on alpha: ICE in spill_failure, at reload1.c:1911)

Your message dated Tue, 13 Jun 2006 17:32:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369810: fixed in gcc-snapshot 20060613-1 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 c

[Bug c++/26559] [4.0/4.1/4.2 Regression] ICE with __builtin_constant_p in template argument

-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |mark at codesourcery dot com |dot org