[Bug middle-end/34969] [4.3 regression] ICE with -fipa-cp -ffast-math

2008-01-29 Thread jakub at gcc dot gnu dot org
--- Comment #8 from jakub at gcc dot gnu dot org 2008-01-29 23:22 --- Fixed. -- jakub at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug middle-end/34969] [4.3 regression] ICE with -fipa-cp -ffast-math

2008-01-29 Thread jakub at gcc dot gnu dot org
--- Comment #7 from jakub at gcc dot gnu dot org 2008-01-29 23:22 --- Subject: Bug 34969 Author: jakub Date: Tue Jan 29 23:21:24 2008 New Revision: 131946 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131946 Log: PR middle-end/34969 * cgraph.h (cgraph_update_edg

[Bug c/35017] [4.3 Regression] PR11377 pedwarns even about valid code

2008-01-29 Thread jakub at gcc dot gnu dot org
--- Comment #7 from jakub at gcc dot gnu dot org 2008-01-29 23:22 --- Fixed. -- jakub at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug target/34526] no-altivec ABI should be fixed or no longer be the default

2008-01-29 Thread janis at gcc dot gnu dot org
--- Comment #3 from janis at gcc dot gnu dot org 2008-01-29 23:45 --- While testing an extremely simple patch for this PR I discovered that -mabi=no-altivec hasn't had an effect since r99284, which changed the way that options are handled for the rs6000 back end. Before that change, rs6

[Bug c++/35022] New: [4.3 regression] ICE with parameter pack in template constant parameter

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following invalid code snippet triggers an ICE on mainline since today: = template class X> void foo(X<0>); = bug.cc:1: error: parameter packs not expanded with `...': bug.c

[Bug c++/35022] [4.3 regression] ICE with parameter pack in template constant parameter

2008-01-29 Thread reichelt at gcc dot gnu dot org
-- reichelt at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35022

[Bug c++/35024] New: [4.3 regression] ICE with parameter pack in nested type

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following invalid code snippet triggers an ICE on mainline since today: = template int foo() { typename T::X x; return x; } void bar() { foo(); } = bug.cc: In functio

[Bug c++/35024] [4.3 regression] ICE with parameter pack in nested type

2008-01-29 Thread reichelt at gcc dot gnu dot org
-- reichelt at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35024

[Bug c++/35026] New: [4.3 regression] ICE with parameter pack in pointer type

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following invalid code snippet is accepted on mainline: = template struct A { T* x[1]; }; A a; = One can also trigger ICEs with the snippet if one compiles it with "-g": bug.cc: In instantiation of 'A': bug.cc:6: in

[Bug c++/35023] [4.3 regression] ICE with parameter pack in variable declaration

2008-01-29 Thread reichelt at gcc dot gnu dot org
-- reichelt at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35023

[Bug c++/35023] New: [4.3 regression] ICE with parameter pack in variable declaration

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following invalid code snippet triggers an ICE on mainline since today: = template int foo() { T t; return t; } void bar() { foo(); } = bug.cc: In function 'int foo()

[Bug c++/35025] New: [4.3 regression] ICE with invalid specialization of variadic template

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following invalid code snippet triggers an ICE on mainline since today: = template struct A; template struct A { A() {} }; = bug.cc:3: error: parameter packs not expanded

[Bug c++/35025] [4.3 regression] ICE with invalid specialization of variadic template

2008-01-29 Thread reichelt at gcc dot gnu dot org
-- reichelt at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35025

[Bug pch/35027] "too short to be a PCH file" warning should be conditional on -Winvalid-PCH

2008-01-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-01-30 00:43 --- I have a simple fix for 4.4.0: Index: c-pch.c === --- c-pch.c (revision 131943) +++ c-pch.c (working copy) @@ -243,8 +243,9 @@ fatal_error

[Bug c++/35026] [4.3 regression] ICE with parameter pack in pointer type

2008-01-29 Thread reichelt at gcc dot gnu dot org
-- reichelt at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35026

[Bug pch/35027] New: "too short to be a PCH file" warning should be conditional on -Winvalid-PCH

2008-01-29 Thread pinskia at gcc dot gnu dot org
If someone puts a .d file in a .gch directory, we will still warn even if the user did not use -Winvalid-PCH. All other reasons why we would reject a PCH including an invalid magic is conditionalized on -Winvalid-PCH so should this warning. -- Summary: "too short to be a PCH file" wa

[Bug target/34982] [4.3 regression] calling a function with undefined parameters causes segmentation fault at -O1 or higher

2008-01-29 Thread tromey at gcc dot gnu dot org
--- Comment #13 from tromey at gcc dot gnu dot org 2008-01-30 01:19 --- > other > than that, I'm not aware of any commonly used K&R bits and pieces in a modern > system. FWIW -- Emacs is mostly K&R. -- tromey at gcc dot gnu dot org changed: What|Removed

[Bug testsuite/34880] gcc.c-torture/execute/float-floor.c fails for targets with no 64-bit double type

2008-01-29 Thread pmarques at grupopie dot com
--- Comment #2 from pmarques at grupopie dot com 2008-01-30 01:03 --- Created an attachment (id=15054) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15054&action=view) fix to float-floor.c Marking all tests that use double as unsupported is actually overkill. The avr target suppor

[Bug testsuite/35005] New testcase execute/20071211-1.c assumes 32 bit integers

2008-01-29 Thread pmarques at grupopie dot com
--- Comment #1 from pmarques at grupopie dot com 2008-01-30 01:07 --- Created an attachment (id=15055) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15055&action=view) proposed patch This proposed patch fixes the problem by using the preprocessor to select the correct type based o

[Bug c++/35028] New: ICE with strange ctor and firstprivate

2008-01-29 Thread reichelt at gcc dot gnu dot org
The following (IMHO valid) code snippet triggers a segfault since GCC 4.2.0 when compiled with "-fopenmp": == struct A { A(); A(const A&, ...); }; void foo() { A a; #pragma omp parallel firstprivate(a) ; } ===

[Bug target/34526] no-altivec ABI should be fixed or no longer be the default

2008-01-29 Thread janis at gcc dot gnu dot org
--- Comment #4 from janis at gcc dot gnu dot org 2008-01-30 01:34 --- TARGET_ALTIVEC_VRSAVE is also set to one in rs6000_override_options after -mno-vrsave has been process, meaning that the option has no effect. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34526

[Bug fortran/34828] ICE: GNU MP: Cannot reallocate memory for gfortran.dg/parameter_array_init_3.f90

2008-01-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2008-01-30 01:56 --- Here is first part of patch that takes care of the segfault. This is also helpful for pr19925: @@ -1051,18 +1054,19 @@ find_array_element (gfc_constructor *con mpz_mul (span, span, tmp); } - if (c

[Bug rtl-optimization/33410] [4.2/4.3 regression] ICE in iv_analyze_expr, at loop-iv.c:934

2008-01-29 Thread tbm at cyrius dot com
--- Comment #7 from tbm at cyrius dot com 2008-01-30 03:16 --- This definitely still ICEs on Alpha: (sid)[EMAIL PROTECTED]:$ /usr/lib/gcc-snapshot/bin/gcc -Wall -O3 -c test.c test.c: In function 'f': test.c:9: internal compiler error: in iv_analyze_expr, at loop-iv.c:935 Please submit a

[Bug fortran/19925] Implied do-loop in an initialization expression is broken

2008-01-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2008-01-30 05:06 --- Regarding the segfault, it is similar to pr34828, but not the same place. Apparently we do not traverse the constructors very well. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19925

[Bug fortran/34945] LBOUND fails for array with KIND(complex) used in zero-sized dimension

2008-01-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-01-30 05:18 --- Reply to comment two: There is front-endery code to do "cond ? a : b" in the handling of missing optional dummy arguments. You can borrow from that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34945

[Bug fortran/34975] [4.3 Regression] Bogus error with USEing modules

2008-01-29 Thread pault at gcc dot gnu dot org
--- Comment #10 from pault at gcc dot gnu dot org 2008-01-30 06:56 --- Subject: Bug 34975 Author: pault Date: Wed Jan 30 06:56:10 2008 New Revision: 131956 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131956 Log: 2008-01-30 Paul Thomas <[EMAIL PROTECTED]> PR fortran

[Bug fortran/34429] Fails: character(len=use_associated_const) function foo()

2008-01-29 Thread pault at gcc dot gnu dot org
--- Comment #8 from pault at gcc dot gnu dot org 2008-01-30 06:56 --- Subject: Bug 34429 Author: pault Date: Wed Jan 30 06:56:10 2008 New Revision: 131956 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131956 Log: 2008-01-30 Paul Thomas <[EMAIL PROTECTED]> PR fortran/

[Bug fortran/34429] Fails: character(len=use_associated_const) function foo()

2008-01-29 Thread pault at gcc dot gnu dot org
--- Comment #9 from pault at gcc dot gnu dot org 2008-01-30 07:03 --- Fixed on trunk Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/34975] [4.3 Regression] Bogus error with USEing modules

2008-01-29 Thread pault at gcc dot gnu dot org
--- Comment #11 from pault at gcc dot gnu dot org 2008-01-30 07:02 --- Fixed on trunk Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Statu

<    1   2