[Bug libfortran/21324] #undef GFC_CLEAR_MEMORY causes testsuite failures

--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-05-03 06:52 --- Patch here: http://gcc.gnu.org/ml/fortran/2005-05/msg00016.html -- What|Removed |Added

[Bug target/21351] internal compiler error with sse

-- What|Removed |Added Component|c++ |target Keywords||ice-on-valid-code, ssemmx http://gcc.gnu.org/bugzilla/

[Bug c++/21351] internal compiler error with sse

--- Additional Comments From js at jeannot dot org 2005-05-03 03:50 --- Created an attachment (id=8802) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8802&action=view) Result of -save-temps -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21351

[Bug c++/21351] New: internal compiler error with sse

When using -msse with g++ 3.4.4 (snapshot of 20050429), an internal compiler error happen: g++34 -v -save-temps -I- -g -O2 -march=pentium4 -mfpmath=sse -msse2 -mmmx -msse -fPIC -Wall -Wpointer-arith -Wcast-qual -Wwrite-strings -Wconversion -pipe -O2 -Iinclude -I/opt/js/devel/COIN/include -I/opt/js/

[Bug other/21350] configure reports only a warning when bison is not installed

--- Additional Comments From peter dot pirkelbauer at tamu dot edu 2005-05-03 02:33 --- automake 1.9 autoconf 2.59a -- What|Removed |Added GCC host triplet|

[Bug other/21350] New: configure reports only a warning when bison is not installed

when bison is not installed, configure reports only a warning, instead of an error. Consequently, the following make-command fails. -- Summary: configure reports only a warning when bison is not installed Product: gcc Version: 4.0.0

[Bug ada/20270] [4.1 Regression] Link error: unsatisfied symbols

--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-05-03 02:11 --- Subject: Re: [4.1 Regression] Link error: unsatisfied symbols > I'm waiting for feedback here; because this is a port-specific proble I can't > test fixes on my own. Patch in bug trail. Sorry for

[Bug ada/20270] [4.1 Regression] Link error: unsatisfied symbols

--- Additional Comments From neroden at gcc dot gnu dot org 2005-05-03 01:33 --- I'm waiting for feedback here; because this is a port-specific proble I can't test fixes on my own. Patch in bug trail. -- What|Removed |Added --

[Bug tree-optimization/15618] Missed bool optimization

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-03 01:16 --- Patch here: . -- What|Removed |Added

[Bug target/20813] [4.1 Regression] ICE in gen_reg_rtx for 3 spec tests

--- Additional Comments From geoffk at gcc dot gnu dot org 2005-05-03 00:58 --- Should be fixed by http://gcc.gnu.org/ml/gcc-patches/2005-05/msg00130.html -- What|Removed |Added

[Bug c++/14329] [tree-ssa] badly formatted warnings for SRA replacements

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 23:51 --- *** Bug 21349 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug c++/21349] Spurious '$' in warning messages

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 23:51 --- (In reply to comment #0) > Compile the source code pasted below with "-Os -Wuninitialized" using C++. > You should get the > following warnings: > > uninit.cpp: In function 'int foo()': > uninit.cpp:13:

[Bug c++/21349] New: Spurious '$' in warning messages

Compile the source code pasted below with "-Os -Wuninitialized" using C++. You should get the following warnings: uninit.cpp: In function 'int foo()': uninit.cpp:13: warning: 'range$begin' is used uninitialized in this function uninit.cpp: In function 'int bar()': uninit.cpp:21: warning: 'range

[Bug tree-optimization/21348] New: tree-vrp.c:has_assert_expr is useless.

Coverage shows: -: 1336:/* Return true if OP is the result of an ASSERT_EXPR that tests the -: 1337: same condition as COND. */ -: 1338: -: 1339:static bool -: 1340:has_assert_expr (tree op, tree cond) 88954: 1341:{ 88954: 1342: tree def_stmt =

[Bug middle-end/21105] [4.0/4.1 Regression] Compiling of large array fails

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 21:55 --- Patch here: . -- What|Removed |Added

[Bug c++/21347] [4.0/4.1 Regression] spurious warning with -Wctor-dtor-privacy

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 21:50 --- Confirmed, this has been failing since "3.5.0 20040909". -- What|Removed |Added

[Bug treelang/21345] [4.0/4.1 Regression] treelang/parse.y:454.11: parse error

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 21:48 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug treelang/21345] [4.0/4.1 Regression] treelang/parse.y:454.11: parse error

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 21:47 --- Subject: Bug 21345 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-02 21:47:48 Modified files: gcc/treelang : Change

[Bug treelang/21345] [4.0/4.1 Regression] treelang/parse.y:454.11: parse error

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 21:47 --- Subject: Bug 21345 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-02 21:47:08 Modified files: gcc/treelang : ChangeLog parse.y Log message:

[Bug c++/21347] spurious warning with -Wctor-dtor-privacy

--- Additional Comments From bh at techhouse dot brown dot edu 2005-05-02 21:44 --- It's also in the main branch -- gcc version 4.1.0 20050501 (experimental). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21347

[Bug treelang/21345] [4.0/4.1 Regression] treelang/parse.y:454.11: parse error

-- What|Removed |Added Summary|[4.0] |[4.0/4.1 Regression] |treelang/parse.y:454.11:|treelang/parse.y:454.11:

[Bug treelang/21345] [4.0] treelang/parse.y:454.11: parse error

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 21:41 --- Confirmed, I see what is wrong, I will apply the obvious patch. This only happens with a recent bison. -- What|Removed |Added --

[Bug c++/21347] New: spurious warning with -Wctor-dtor-privacy

cat > foo.cpp << EOF class A { public: int x; int getX() { return x; } // comment out to avoid warning }; int foo() { A a; // accepted: clearly the ctor is not private return a.x; } EOF g++ -c -Wctor-dtor-privacy foo.cpp foo.cpp:1: warning: 'class A' only defines private constr

[Bug ada/21346] New: Ada.Directories.Compose raises exception if Containing_Directory is empty string

Making a call to subprogram Ada.Directories.Compose with an empty string (the default value) for the parameter "Containing_Directory" leads to a Name_Error exception being raised. -- Test Program with Ada.Directories; with Ada.Text_IO; procedure Test_Compose is Result : String := Ada.Directori

[Bug bootstrap/21345] New: [4.0.0] treelang/parse.y:454.11: parse error

Hi, I got the following during bootstrap: bison -v --defines --output=treelang/parse.c /home/ltg/software/src/work/gcc-4.0.0/gcc/treelang/parse.y /home/ltg/software/src/work/gcc-4.0.0/gcc/treelang/parse.y:454.11: parse error, unexpected ":", expecting ";" or "|" make[2]: [treelang/parse.h] Error

[Bug target/21344] Libgcc file name not returned correctly

-- What|Removed |Added Component|c |target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21344

[Bug c/21344] New: Libgcc file name not returned correctly

The command shown below does not return the correct Thumb libgcc library for gcc v4.0.0: $ /3rd/arm-elf-gcc/bin/arm-thumb-elf-gcc -mthumb -print-libgcc-file-name /Volumes/Misc/3rd/arm-elf-gcc/bin/../lib/gcc/arm-thumb-elf/4.0.0/libgcc.a The same command used with gcc v3.4.3 does return the correc

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 20:02 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug c/21343] New: [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

My fix to bug 13801 caused the compiler no longer to diagnose incompatible refinements in nested scopes of the types of objects or functions with internal linkage. (Fixing this involves adding a special "internal scope", like the "external scope", which stores the full composite type information f

[Bug c/21342] [4.0/4.1 Regression] some incompatible external declarations not diagnosed

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 20:00 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug c/21342] New: [4.0/4.1 Regression] some incompatible external declarations not diagnosed

My fix to bug 13801 caused some cases of incompatible declarations with external linkage (in different scopes) not to be diagnosed. pushdecl fails to update the type in the external scope with the new information from the new declaration if there was already a declaration in the current scope, or

[Bug c/15698] [4.0/4.1 Regression] no error in presence of broken builtin fn + K&R declaration

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 19:51 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug c/15698] [4.0/4.1 Regression] no error in presence of broken builtin fn + K&R declaration

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 19:45 --- Subject: Bug 15698 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-02 19:45:27 Modified files: gcc: Change

[Bug c/15698] [4.0/4.1 Regression] no error in presence of broken builtin fn + K&R declaration

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 19:39 --- Subject: Bug 15698 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-02 19:39:04 Modified files: gcc: ChangeLog c-decl.c c-tree.h

[Bug c++/21120] Empty declaration with typeof accepted

--- Additional Comments From gdr at integrable-solutions dot net 2005-05-02 19:09 --- Subject: Re: Empty declaration with typeof accepted "bangerth at dealii dot org" <[EMAIL PROTECTED]> writes: | Confirmed. Funny enough, icc accepts the code as well... would there be compilers unio

[Bug tree-optimization/21341] [4.1 Regression] gcc.dg/tree-ssa/loop-4.c scan-tree-dump-times arr_base.[^0][^\n\r]*= 0 fails

-- What|Removed |Added CC||rakdver at gcc dot gnu dot ||org, pinskia at gcc dot gnu

[Bug c++/21057] iso C99 complex double: problems with g++

--- Additional Comments From bangerth at dealii dot org 2005-05-02 19:02 --- Confirmed. However, this has really low priority: the C++ standard is not a superset of the C99 standard, so a number of things new to C99 are not part of C++, and this is one of them. If you want to write por

[Bug middle-end/19985] [3.4/4.0/4.1 Regression] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit ()

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 19:02 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

Re: fortran internal error: backend decl for variable ... exists:

On May 2, 2005, at 2:06 PM, Steffen Seeger wrote: Hello everybody, I have successfully built gcc-4.0.0 out of the release tar-file (complete distribution) on an athlon system targeting i386-scientific-linux. The C and C++ parts work like a charm so far, compiling substantial amounts of C/C++ code w

[Bug c++/21120] Empty declaration with typeof accepted

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:56 --- Confirmed. Funny enough, icc accepts the code as well... W. -- What|Removed |Added

[Bug c++/21146] unable to resolve visible symbol

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:54 --- What is going wrong is this: the name 'S' may refer to both the local typedef in the base class 'A' as well as to the global structure '::S'. If I write either friend class A< A< ::S>::S>; or friend cl

[Bug tree-optimization/15017] [tree-ssa] compare (equal) with casts are not removed

--- Additional Comments From dann at godzilla dot ics dot uci dot edu 2005-05-02 18:51 --- Comment #3 in PR15484 has a reference to a patch that might fix the cause for some of these issues. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15017

[Bug c++/21174] name lookup differs between namespace-scope and global scope

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:48 --- Just like PR 21205. W. -- What|Removed |Added Status|UNCONFIRMED |

[Bug c++/21204] using-directive does not honor name selection via using-declaration

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:47 --- Same problem as in PR 21205. W. -- What|Removed |Added Status|UNCONFIRMED

[Bug c++/21205] using-directive does not honor name selection via typedef

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:46 --- The problem is in fact that 'S' is ambiguous: either N::S or M::S are candidates. The fact that gcc says that it doesn't know names when in fact it does but they are ambiguous is recorded in a number of other

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From gdr at integrable-solutions dot net 2005-05-02 18:45 --- Subject: Re: Lack of Posix compliant thread safety in std::basic_string "pcarlini at suse dot de" <[EMAIL PROTECTED]> writes: | --- Additional Comments From pcarlini at suse dot de 2005-05-02 17

[Bug c++/21337] [3.4 Regression] ICE on valid code when using boost::bind

-- Bug 21337 depends on bug 21339, which changed state. Bug 21339 Summary: [3.4 regression] ICE with pointer to member in template http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21339 What|Old Value |New Value --

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-05-02 18:44 --- Fixed in 3.4.4. See PR 15875 for the patch. -- What|Removed |Added Status|ASSI

[Bug c++/21279] static Derived-to-Base cast fails when ~Derived has run.

--- Additional Comments From bangerth at dealii dot org 2005-05-02 18:42 --- I would be very much surprised if this was allowed. But then I, too, can't find any normative statements in the standard. Maybe looking at the wrong places, though... W. -- http://gcc.gnu.org/bugzilla/

[Bug c++/15875] [3.4/4.0 Regression] rejects pointer to member in template

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 18:39 --- Subject: Bug 15875 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-3_4-branch Changes by: [EMAIL PROTECTED] 2005-05-02 18:38:54 Modified files: gcc/cp : Change

[Bug libstdc++/21251] Placement into shared memory

--- Additional Comments From pcarlini at suse dot de 2005-05-02 18:10 --- Marc, we are talking about two completely different issues. Indeed, it's *perfectly* possible using a shared-memory allocator with the STL containers. In fact, we are in the process of providing an allocator of tha

[Bug middle-end/19985] [3.4/4.0/4.1 Regression] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit ()

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 18:09 --- Subject: Bug 19985 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-3_4-branch Changes by: [EMAIL PROTECTED] 2005-05-02 18:08:50 Modified files: gcc: gcov-i

[Bug tree-optimization/21294] Missed removal of null pointer check

--- Additional Comments From kazu at cs dot umass dot edu 2005-05-02 18:07 --- Just checked in a patch. -- What|Removed |Added Status|ASSIGNED

[Bug tree-optimization/21294] Missed removal of null pointer check

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 18:06 --- Subject: Bug 21294 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-02 18:06:28 Modified files: gcc: ChangeLog tree-vrp.c gcc/tes

fortran internal error: backend decl for variable ... exists:

Hello everybody, I have successfully built gcc-4.0.0 out of the release tar-file (complete distribution) on an athlon system targeting i386-scientific-linux. The C and C++ parts work like a charm so far, compiling substantial amounts of C/C++ code without noticeable glitches. Congratulations and

[Bug middle-end/19985] [3.4/4.0/4.1 Regression] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit ()

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 18:05 --- Subject: Bug 19985 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-02 18:05:28 Modified files: gcc: gcov-i

[Bug middle-end/19985] [3.4/4.0/4.1 Regression] executables created with -fprofile-arcs -ftest-coverage segfault in gcov_exit ()

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 18:02 --- Subject: Bug 19985 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-02 18:02:48 Modified files: gcc: gcov-io.h ChangeLog Log message:

[Bug bootstrap/21288] bootstrap issues with profiledbootstrap

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 18:01 --- (In reply to comment #1) > I get the same error with 'make bootstrap' -- it's not the profiling that > causes > the ICE. Similarly, I get the same error when I download the full tar file, > so > it's also

[Bug bootstrap/21288] bootstrap issues with profiledbootstrap

--- Additional Comments From bh at techhouse dot brown dot edu 2005-05-02 17:58 --- I get the same error with 'make bootstrap' -- it's not the profiling that causes the ICE. Similarly, I get the same error when I download the full tar file, so it's also not a packaging bug. If there's

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From pcarlini at suse dot de 2005-05-02 17:33 --- About the last issue, besided confidential information, there is this nice public thread that nicely summarizes it: http://tinyurl.com/9o4oj -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From pcarlini at suse dot de 2005-05-02 17:23 --- > I don't quite understand why you want to see this issue as a memory > management policy issue, as opposed to a thread safety issue. Whatever, after all that is the layer at which you actually do the low-level m

[Bug middle-end/21265] [4.0/4.1 regression] GCC fails to optimize tail call to memset

-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org |dot org | Status|NEW

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From gdr at integrable-solutions dot net 2005-05-02 17:17 --- Subject: Re: Lack of Posix compliant thread safety in std::basic_string "pcarlini at suse dot de" <[EMAIL PROTECTED]> writes: | --- Additional Comments From pcarlini at suse dot de 2005-05-02 17

[Bug c++/21340] [4.0/4.1 Regression] error in constructor lookup (can't find constructor with "const void**" argument)

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 17:15 --- Confirmed, reduced testcase: struct Base{}; struct Iterator : virtual Base {}; bool operator==(const Iterator&, const Iterator&); struct IteratorI : Iterator {}; struct Obj { bool operator==(const Obj&)

[Bug tree-optimization/21293] [4.0 Regression] ICE in set_value_handle

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 17:15 --- Subject: Bug 21293 CVSROOT:/cvs/gcc Module name:gcc Branch: apple-local-200502-branch Changes by: [EMAIL PROTECTED] 2005-05-02 17:15:15 Modified files: gcc

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From pcarlini at suse dot de 2005-05-02 17:01 --- > You probably got the mail about users saying that he read on C++ > newsgroups that V3-s implementation of std::string is known to be > avoided in multi-threaded programs. Whereas I'm all for providing alternate

[Bug tree-optimization/20947] [4.1 Regression] ICE in check_loop_closed_ssa_use, at tree-ssa-loop-manip.c:394 with -ftree-vectorize

--- Additional Comments From janis at gcc dot gnu dot org 2005-05-02 16:53 --- The SPEC CPU2000 failures reported in 21054, on which the testcase in comment #5 is based, stopped on 20050423. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20947

[Bug tree-optimization/21341] New: [4.1 Regression] gcc.dg/tree-ssa/loop-4.c scan-tree-dump-times arr_base.[^0][^\n\r]*= 0 fails

The following FAIL has appeared on mainline between 20050501 and 20050502 on targets including i686-pc-linux-gnu and hppa64-hpux. gcc-testresults will probably show more targets. FAIL: gcc.dg/tree-ssa/loop-4.c scan-tree-dump-times arr_base.[^0][^\n\r]*= 0 -- Summary: [4.1 Regression

[Bug libstdc++/21251] Placement into shared memory

--- Additional Comments From mronell at alumni dot upenn dot edu 2005-05-02 16:49 --- Apologies for my persistence, but the following is still not clear to me. Given the last reply to this concern, I now understand: 1. Placement into shared memory is not possible. If processes

[Bug tree-optimization/17116] Missed jump threading/bypassing optimization with loop and % (or ands)

--- Additional Comments From law at redhat dot com 2005-05-02 16:46 --- Subject: Re: Missed jump threading/bypassing optimization with loop and % (or ands) On Sun, 2005-05-01 at 16:29 +, pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc

[Bug target/21325] [4.0 Regression] libjava should be re-enabled for ppc-darwin

--- Additional Comments From mckinlay at redhat dot com 2005-05-02 16:44 --- It sounds like this is just a matter of testing that it really does work now. Pinskia: If you could test/post a patch, that would be great. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21325

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From gdr at integrable-solutions dot net 2005-05-02 16:40 --- Subject: Re: Lack of Posix compliant thread safety in std::basic_string "rittle at latour dot waar dot labs dot mot dot com" <[EMAIL PROTECTED]> writes: | Subject: Re: New: Lack of Posix compliant t

[Bug c++/21274] SSA Crash, reproducable

--- Additional Comments From callahan at sci dot utah dot edu 2005-05-02 16:36 --- I suspect that this is an x86-64 bug. I have a different computer available to me here. I get the same result as Dorit. Note that it appears to be the same Ubuntu beta version as the x86-64 version. I

[Bug c++/21340] New: error in constructor lookup (can't find constructor with "const void**" argument)

Ice for C++ from ZeroC (http://www.zeroc.com, source code available) doesn't compile anymore with GCC 4.0.0 (I also tried with GCC from CVS and the result is the same). It compiled fine with GCC 3.4.2. I'm getting an error which looks like the following with 4.0.0: Main.cpp: In constructor 'I

[Bug libfortran/18122] [4.0 only] gfortran internal error in namelist read

--- Additional Comments From doko at cs dot tu-berlin dot de 2005-05-02 16:29 --- Subject: Re: [4.0 only] gfortran internal error in namelist read pault at gcc dot gnu dot org writes: > > --- Additional Comments From pault at gcc dot gnu dot org 2005-04-23 > 16:16 --- > The

[Bug c++/21274] SSA Crash, reproducable

--- Additional Comments From dorit at il dot ibm dot com 2005-05-02 16:27 --- Thanks for the testcase. I tried reproducing the problem on i686-pc-linux-gnu with today's snapshot of 4.1, and also with today's snapshot of 4.0 (gcc version 4.0.1 20050502 (prerelease))

[Bug tree-optimization/20947] [4.1 Regression] ICE in check_loop_closed_ssa_use, at tree-ssa-loop-manip.c:394 with -ftree-vectorize

--- Additional Comments From dorit at il dot ibm dot com 2005-05-02 16:06 --- I can't reproduce this problem - not for the testcase in comment #3 and not for the testcase in comment #5 (I tried on i686-pc-linux-gnu and on powerpc-apple- darwin). Does the problem still occur? -- http

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From rittle at latour dot waar dot labs dot mot dot com 2005-05-02 16:02 --- Subject: Re: New: Lack of Posix compliant thread safety in std::basic_string >I am sending this to the g++ bug list on the recommendation of >Gabriel Dos Reis. From what little

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-05-02 15:53 --- > Just curious: where can I get more information about this issue? We were > linking our shared library statically with libgcc_eh.a in the past with no > problems, and many people on different machines suc

[Bug bootstrap/21268] [4.0/4.1 Regression] Bootstrap, configuration problem and insn-conditions.c

--- Additional Comments From v dot haisman at sh dot cvut dot cz 2005-05-02 15:52 --- Subject: Re: [4.0/4.1 Regression] Bootstrap, configuration problem and insn-conditions.c That I don't have it set imho can be seen from config.log: ac_cv_env_CPPFLAGS_set= On Mon, 2 May 2005, pin

[Bug c++/15875] [3.4/4.0 Regression] rejects pointer to member in template

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 15:40 --- Subject: Bug 15875 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-02 15:40:25 Modified files: gcc/testsuite : Change

[Bug c++/15875] [3.4/4.0 Regression] rejects pointer to member in template

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 15:38 --- Subject: Bug 15875 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-02 15:38:38 Modified files: gcc/testsuite : ChangeLog Added files: gcc/t

[Bug bootstrap/21268] [4.0/4.1 Regression] Bootstrap, configuration problem and insn-conditions.c

--- Additional Comments From v dot haisman at sh dot cvut dot cz 2005-05-02 15:30 --- Subject: Re: [4.0/4.1 Regression] Bootstrap, configuration problem and insn-conditions.c Nope, my environment is clean wrt/ compiler flags. On Mon, 2 May 2005, pinskia at gcc dot gnu dot org wrote

[Bug tree-optimization/21030] [4.1 Regression] ICE in set_value_range building 176.gcc with -O2

--- Additional Comments From dnovillo at redhat dot com 2005-05-02 15:29 --- Subject: Re: [4.1 Regression] ICE in set_value_range building 176.gcc with -O2 On Fri, Apr 29, 2005 at 07:57:43PM -, ro at techfak dot uni-bielefeld dot de wrote: > Unfortunately, even with the patch app

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |mark at codesourcery dot com |dot org | Status|NEW

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

--- Additional Comments From mark at codesourcery dot com 2005-05-02 14:56 --- Subject: Re: New: [3.4 regression] ICE with pointer to member in template reichelt at gcc dot gnu dot org wrote: > The testcase in PR 15875 started ICE'ing on the 3.4 branch again: > Mark, this is most pro

[Bug bootstrap/21335] bootstrap fails with CFLAGS="-O3 -ftree-vectorize"

--- Additional Comments From dorit at il dot ibm dot com 2005-05-02 14:51 --- I get the following bootstrap failure on powerpc-apple-darwin, with "-O2 -ftree- vectorize": ../../gcc/gcc/builtins.c: In function 'fold_builtin_1': ../../gcc/gcc/builtins.c:8451: internal compiler error: Bus

[Bug c++/19991] [3.4 regression] Enum not accepted in array-size

--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-05-02 14:48 --- Fixed in 3.4.4. -- What|Removed |Added Status|ASSIGNED|RESO

[Bug c++/19991] [3.4 regression] Enum not accepted in array-size

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-02 14:47 --- Subject: Bug 19991 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-3_4-branch Changes by: [EMAIL PROTECTED] 2005-05-02 14:46:48 Modified files: gcc/cp : Change

[Bug libfortran/18958] [4.0 only] eoshift segfaults when shifting off the end of an array

-- What|Removed |Added Known to fail||4.0.0 Known to work||4.1.0 Summary|eoshift segfaults when |[4

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From gdr at gcc dot gnu dot org 2005-05-02 14:42 --- (In reply to comment #9) > Does the C++ standard mention multithreading and Posix threads? ;) That is a very uninteresting question. You're quite right that the C++ standard does not mention usability, though.

[Bug libfortran/21324] #undef GFC_CLEAR_MEMORY causes testsuite failures

--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-05-02 14:29 --- Created an attachment (id=8801) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8801&action=view) Proposed patch -- What|Removed |Added -

[Bug c++/21089] [4.0/4.1 Regression] C++ front-end does not "inline" the static const double

-- What|Removed |Added Status|REOPENED|NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21089

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

--- Additional Comments From pcarlini at suse dot de 2005-05-02 14:20 --- Does the C++ standard mention multithreading and Posix threads? ;) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 14:19 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 14:18 --- *** Bug 21337 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug c++/21337] [3.4 Regression] ICE on valid code when using boost::bind

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 14:18 --- Yes this is a dup of bug 21339. *** This bug has been marked as a duplicate of 21339 *** -- What|Removed |Added -

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

-- What|Removed |Added Known to work||3.4.3 4.1.0 4.0.0 Target Milestone|--- |3.4.4 http://gcc.gnu.org/bugzilla/show_bug.

[Bug c++/21339] [3.4 regression] ICE with pointer to member in template

-- What|Removed |Added OtherBugsDependingO||21337 nThis|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21339

[Bug c++/21337] [3.4 Regression] ICE on valid code when using boost::bind

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-02 14:15 --- This is most likely the same as PR 21339. -- What|Removed |Added BugsThisDependsOn|

  1   2   >