tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44380
tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44381
tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44383
tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44387
tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44388
tedBy: avenikov at gmail dot com
GCC host triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
GCC target triplet: x86-64, Linux 2.6.18 (Suse 11.0), gcc 4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44389
--- Comment #7 from avenikov at gmail dot com 2010-06-02 15:36 ---
Sorry, I've just noticed that I messed up.
I was clicking the "refresh" button to see the status of the bug and apparently
that was creating new bug report every time.
Sorry for that.
--
http://gcc.g