Bug#406550: www.kaka.hw.hu
www.kaka.hw.hu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package gcc-4.2
# # bts-link upstream status pull for source package gcc-4.2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #425608 # * http://gcc.gnu.org/PR32072 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> INVALID # * closed upstream tags 425608 + fixed-upstream usertags 425608 + status-RESOLVED resolution-INVALID thanks
Processed: [bts-link] source package gcc-4.2
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.2 > # 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 for #425608 > # * http://gcc.gnu.org/PR32072 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> INVALID > # * closed upstream > tags 425608 + fixed-upstream Bug#425608: g++-4.2: fails to compile some code with -O3 while -O2 works There were no tags set. Tags added: fixed-upstream > usertags 425608 + status-RESOLVED resolution-INVALID Bug#425608: g++-4.2: fails to compile some code with -O3 while -O2 works There were no usertags set. Usertags are now: resolution-INVALID status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 for #390693 > # * http://gcc.gnu.org/PR27880 > # * remote status changed: REOPENED -> NEW > usertags 390693 - status-REOPENED Bug number 390693 not found. (Is it archived?) > usertags 390693 + status-NEW Bug number 390693 not found. (Is it archived?) > # remote status report for #428926 > # * http://gcc.gnu.org/PR32509 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 428926 + fixed-upstream Bug#428926: gmp: FTBFS: /usr/include/c++/4.1.3/bits/locale_facets.h:1682: undefined reference to `std::numpunct::_M_initialize_numpunct(__locale_struct*)' There were no tags set. Tags added: fixed-upstream > usertags 428926 + status-RESOLVED resolution-FIXED Bug#428926: gmp: FTBFS: /usr/include/c++/4.1.3/bits/locale_facets.h:1682: undefined reference to `std::numpunct::_M_initialize_numpunct(__locale_struct*)' There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[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 #390693 # * http://gcc.gnu.org/PR27880 # * remote status changed: REOPENED -> NEW usertags 390693 - status-REOPENED usertags 390693 + status-NEW # remote status report for #428926 # * http://gcc.gnu.org/PR32509 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 428926 + fixed-upstream usertags 428926 + status-RESOLVED resolution-FIXED thanks
Processed: Re: GCC Spec File for Profiling
Processing commands for [EMAIL PROTECTED]: > reopen 433539 Bug#433539: gcc-4.1: profiling support on hurd 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433539: GCC Spec File for Profiling
reopen 433539
thanks
Hello!
On Sat, Jul 14, 2007 at 10:49:13AM -0400, Michael Casadevall wrote:
> After some trail and error as well as reading up how static binaries work
> and the difference between gcrt0 and gcrt1, I was able to fix the profiling
> bug with a GCC spec file:
Are you sure you did check static compiling?
Your patch is now the the Debian gcc-4.1 package and it fails like this
for me when I try to build static executables:
#v+
$ gcc -static -x c /dev/null
gcc: spec failure: unrecognized spec option 'p'
/usr/bin/ld: {:gcrt0}: No such file: No such file or directory
collect2: ld returned 1 exit status
#v-
> %rename startfile old_startfile
>
> *startfile: %{!shared: %{!static: %{pg:gcrt0.o%s} %{!pg:%{p:gcrt0.o%s}
> %{!p:crt1.o%s}}} %{static: %{pg:gcrt0.o%s} %{!pg:{%p:gcrt0}}
Here is a typo, I suppose: ^
> %{!p:crt0.o%s}}} crti.o%s %{static:crtbeginT.o%s}
> %{!static:%{!shared:crtbegin.o%s} %{shared:crtbeginS.o%s}}
>
> For those of you who know how Hurd handles statically linked binaries,
> you'll probably find it weird that we only link against gcrt0. The reason
> behind that is that the profiling code in GCC only works against static
> binaries; it doesn't support shared binaries. This is my first time ever
> messing around with GCC (or writing a spec file) so I'd be intersted in
> hearing some feedback. I already figured out howto change GCCs internal
> specs file to include this change, but I wanted to hear from the experts
> before I submit a patch.
I also didn't look it up so far and without doing so don't know offhand
which of the crt files are to be used under which circumstances. I can
only tell you that previous discussions about this took place on
.
Regards,
Thomas
signature.asc
Description: Digital signature
Bug#431608: Some statistics
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, compiling parts of python-qt4 yields the following results: g++ 4.1.3: 13,71s user 0,26s sys gcc-snapshot: 1m59,38s user 0,69s sys The preprocessed source code used above is rather large, please get it from here: http://diotavelli.net/files/sipQtCorepart0.E.bz2 best, Torsten - -- Torsten Marek <[EMAIL PROTECTED]> ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858 Keyserver: subkeys.pgp.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGrPzPfMVFHqJEyFgRAgalAJ9LciHbMeViSKlv2xheRH1vnRrYNACfcqj/ HZkagUVrf5QWznUwEVBHdOg= =Ramb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431608: Some statistics
Torsten Marek writes: > compiling parts of python-qt4 yields the following results: > > g++ 4.1.3: 13,71s user 0,26s sys > gcc-snapshot: 1m59,38s user 0,69s sys thanks, the report is forwarded. Would it be possible to let sip-qt* to use g++-4.1 explicitely? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431608: Some statistics
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Klose schrieb: > Torsten Marek writes: >> compiling parts of python-qt4 yields the following results: >> >> g++ 4.1.3: 13,71s user 0,26s sys >> gcc-snapshot: 1m59,38s user 0,69s sys > > thanks, the report is forwarded. Would it be possible to let sip-qt* > to use g++-4.1 explicitely? Hi, I wouldn't know a reason why that should be a problem for the time being. I'll also talk to upstream if they are aware of the problems. best, Torsten - -- Torsten Marek <[EMAIL PROTECTED]> ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858 Keyserver: subkeys.pgp.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGrQNNfMVFHqJEyFgRAuXpAKDC2LW/8ElVEc3f/hdMWVxlWm5hoACePNJj K/ncE1bUVMs3OXctC4tAtH4= =g+Cb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: notfound 373937 in 4.1.1-5
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > notfound 373937 4.1.1-5 Bug#373937: libstdc++6: codecvt locale facet is broken Bug marked as not found in version 4.1.1-5. (By the way, this Bug is currently marked as done.) > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 401585 in 4.1.1ds2-22
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > fixed 401585 4.1.1ds2-22 Bug#401585: [m68k] ICE: in reload, at reload1.c:1079 Bug marked as fixed in version 4.1.1ds2-22. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 400031 in 4.1.1ds2-22
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > fixed 400031 4.1.1ds2-22 Bug#400031: gcc-4.1: Enable -pthread for GNU/Hurd Bug marked as fixed in version 4.1.1ds2-22. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
