[Bug middle-end/26836] New: ICE on valid code (tree type is null in tree-gimple.c)

Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26836

[Bug middle-end/26835] New: ICE in f951 on valid code at -O2 -ftree-loop-linear

roduct: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet

[Bug middle-end/26817] New: ICE in verify_ssa

4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC

[Bug other/26601] New: --whole-program --combine with gcc4.1 fails to link cpu2000 benchmarks

gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26601

[Bug fortran/26550] New: ICE in gimplify_expr() on valid code

u dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26550

[Bug regression/26435] New: ICE with -O1 -ftree-loop-linear and higher optimization

Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: regression AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64

[Bug other/26327] memory leaks

--- Comment #2 from uttamp at us dot ibm dot com 2006-02-21 19:51 --- patch posted, http://gcc.gnu.org/ml/gcc-patches/2006-02/msg01377.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26327

[Bug other/26327] New: memory leaks

cc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-li

[Bug other/26147] another memory leak

--- Comment #4 from uttamp at us dot ibm dot com 2006-02-16 00:35 --- Subject: Re: another memory leak > > --- Comment #3 from pinskia at gcc dot gnu dot org 2006-02-15 23:09 > --- > Fixed. > > dist_v and init_v are GC pointers so they don't

[Bug other/26184] memory leaks in swing modulo scheduling function

--- Comment #2 from uttamp at us dot ibm dot com 2006-02-08 22:44 --- I'll submit a patch to fix these leaks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26184

[Bug other/26184] memory leaks in swing modulo scheduling function

--- Comment #1 from uttamp at us dot ibm dot com 2006-02-08 22:43 --- I missed another memory leak in the same file, in function generate_reg_moves(), memory pointed by uses_of_defs is not freed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26184

[Bug other/26184] New: memory leaks in swing modulo scheduling function

us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26184

[Bug tree-optimization/26147] New: another memory leak

gnedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26147

[Bug c/26145] New: memory leak in loop unswitching.

IRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26145

[Bug tree-optimization/25962] New: Pointer (null) check after the use

Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25962

[Bug tree-optimization/25937] ICE with -O2 -ftree-loop-linear

--- Comment #5 from uttamp at us dot ibm dot com 2006-01-25 23:14 --- I put the line numbers in there because I just wanted to point out the different error messages I get with small changes in code. ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25937

[Bug c/25929] ICE with -ftree-loop-linear

--- Comment #3 from uttamp at us dot ibm dot com 2006-01-25 16:56 --- Reduced test case int vq_index(float *in, const float *codebook, int len, int entries) { int i,j; int best_index=0; for (i=0;i /opt/gcc-nightly/trunk-20060123/bin/gcc -O1 -ftree-loop-linear -c ccbdYzn2.c

[Bug tree-optimization/25937] ICE: Illegal instruction, with valid code

--- Comment #1 from uttamp at us dot ibm dot com 2006-01-24 01:58 --- fyi: This works till trunk-20060106. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25937

[Bug tree-optimization/25937] New: ICE: Illegal instruction, with valid code

://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE: Illegal instruction, with valid code Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assign

[Bug c/25933] New: memory leaks

tatus: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-lin

[Bug c++/11987] [3.4/4.0/4.1/4.2 regression] Accepts-invalid with inherited nested type

--- Comment #10 from uttamp at us dot ibm dot com 2006-01-23 19:20 --- Just for the information. I tested this bug against following branches, gcc-3.2.3 - causes an ICE gcc-3.4.0 - no ICE gcc-3.4.2 - no ICE gcc-3.4.3 - no ICE gcc-4.0.0 - no ICE gcc-4.1.0 - no ICE gcc-4.0.2 - no ICE

[Bug middle-end/23785] [4.1/4.2 Regression] 197.parser performance drop

--- Comment #6 from uttamp at us dot ibm dot com 2006-01-17 00:42 --- With the latest mainline, the performance numbers for parser benchmark are very close to the reported numbers (on July 29th 2005). With the mainline, parser numbers on powerpc64-linux with "-O3 -m32 -mcpu=p

[Bug middle-end/24565] [4.1/4.2 Regression] facerec performance regression

--- Comment #8 from uttamp at us dot ibm dot com 2006-01-16 23:56 --- I'm closing this bug as FIXED since the current facerec benchmark numbers on powerpc64-linux seems to be lot closer to the numbers generatged in Oct 2005 (before reported regression happen). -- uttamp at u

[Bug middle-end/24565] [4.1/4.2 Regression] facerec performance regression

--- Comment #6 from uttamp at us dot ibm dot com 2006-01-16 18:19 --- Steve, The numbers have changed since the last time I saw them. The current facerec perf. numbers are much close to the Oct. when I reported it. Do we still want me to investigate this any further? -- http

[Bug fortran/24886] another runtime error goes undetected

--- Comment #6 from uttamp at us dot ibm dot com 2006-01-11 22:02 --- Subject: Re: another runtime error goes undetected On Wed, 2006-01-11 at 09:07 +, pault at gcc dot gnu dot org wrote: > > --- Comment #5 from pault at gcc dot gnu dot org 2006-01-11 09:07 ---

[Bug rtl-optimization/25578] [4.2 Regression] gfortran version 4.2.0 20051227 - 144 new testsuite failures since 2005121

--- Comment #10 from uttamp at us dot ibm dot com 2006-01-04 16:52 --- *** Bug 25656 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25578

[Bug middle-end/25656] runtime error with 191.fma3d benchmark

--- Comment #5 from uttamp at us dot ibm dot com 2006-01-04 16:52 --- *** This bug has been marked as a duplicate of 25578 *** -- uttamp at us dot ibm dot com changed: What|Removed |Added

[Bug rtl-optimization/25578] [4.2 Regression] gfortran version 4.2.0 20051227 - 144 new testsuite failures since 2005121

--- Comment #9 from uttamp at us dot ibm dot com 2006-01-04 16:51 --- *** Bug 25657 has been marked as a duplicate of this bug. *** -- uttamp at us dot ibm dot com changed: What|Removed |Added

[Bug middle-end/25657] runtime error with 200.sixtrack benchmark

--- Comment #9 from uttamp at us dot ibm dot com 2006-01-04 16:51 --- *** This bug has been marked as a duplicate of 25578 *** -- uttamp at us dot ibm dot com changed: What|Removed |Added

[Bug middle-end/25656] runtime error with 191.fma3d benchmark

--- Comment #4 from uttamp at us dot ibm dot com 2006-01-04 16:50 --- This has been fixed with todays mainline tree. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25656

[Bug middle-end/25657] runtime error with 200.sixtrack benchmark

--- Comment #8 from uttamp at us dot ibm dot com 2006-01-04 16:50 --- This has been fixed with todays mainline tree. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25657

[Bug middle-end/25657] runtime error with 200.sixtrack benchmark

--- Comment #7 from uttamp at us dot ibm dot com 2006-01-04 02:02 --- Yes, I'll. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25657

[Bug middle-end/25656] runtime error with 191.fma3d benchmark

--- Comment #3 from uttamp at us dot ibm dot com 2006-01-04 01:47 --- peak options are, "-O3 -mcpu=power4 -ffast-math -ftree-loop-linear -funroll-loops -fpeel-loops -m32" base options are, "-O2 -mcpu=power4 -m32" -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25656

[Bug middle-end/25657] runtime error with 200.sixtrack benchmark

--- Comment #3 from uttamp at us dot ibm dot com 2006-01-04 01:46 --- peak options are, "-O3 -mcpu=power4 -ffast-math -ftree-loop-linear -funroll-loops -fpeel-loops -m32" base options are, "-O2 -mcpu=power4 -m32" -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25657

[Bug middle-end/25657] New: runtime error with 200.sixtrack benchmark

gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25657

[Bug middle-end/25656] New: runtime error with 191.fma3d benchmark

Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC

[Bug middle-end/24565] [4.1/4.2 Regression] facerec performance regression

--- Comment #4 from uttamp at us dot ibm dot com 2005-12-22 14:11 --- Sorry for the delay and I never expected that someone else will figure it out for me. It just that I got distracted doing other things and right now I'm on vacation. I don't have access to the machine where

[Bug fortran/20839] do-loop with do-construct-name needs needs end do

--- Comment #4 from uttamp at us dot ibm dot com 2005-12-09 21:40 --- I did build and completed the regression test. The patch in comment #3 fixes this problem (when compiled with -pedantic option) but gfortran still fails to report this as an error with -std=f95 without -pedantic

[Bug fortran/25321] New: array shape conformance error

different types. -- Summary: array shape conformance error Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: u

[Bug fortran/25319] New: namelist error

Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: po

[Bug regression/25252] New: ICE on invalid code

0x10093900 in main (argc=Variable "argc" is not available. ) at /home/gccbuild/gcc_trunk_anonsvn/trunk/gcc/main.c:35 (gdb) -- Summary: ICE on invalid code Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P

[Bug regression/24978] New: ICE in gfc_assign_data_value_range

MED Severity: normal Priority: P3 Component: regression AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux h

[Bug fortran/24936] New: Internal error

ortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24936

[Bug fortran/24886] another runtime error goes undetected

--- Comment #2 from uttamp at us dot ibm dot com 2005-11-16 17:33 --- Any error which indicates something like, "dummy argument defined to be larger than actual argument. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24886

[Bug fortran/24886] New: another runtime error goes undetected

d Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64

[Bug fortran/24885] New: fails to report runtime error

eportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24885

[Bug fortran/24884] New: compiles invalid-code

Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24884

[Bug fortran/24878] New: subroutine getting called illegally as a function

a function Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-l

[Bug fortran/24866] New: internal compiler error

Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-l

[Bug fortran/24806] New: accepts invalid DO construct code

Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powepc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64

[Bug fortran/24646] New: accepting invalid label

nedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24646

[Bug fortran/24641] New: rejecting valid code

Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: power

[Bug fortran/24640] New: ice with invalid label

lid label Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC

[Bug regression/24565] New: facerec performance regression

u dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24565

[Bug fortran/24447] dimag_ undefined error with -std=f95

--- Comment #7 from uttamp at us dot ibm dot com 2005-10-20 01:10 --- Finally I found the f95 standard document (1539-1-1997) and did not see dimag() mentioned in there. I was looking at PGI Fortran Reference document all this time and there was not comment about dimag() as an extension

[Bug fortran/24447] dimag_ undefined error with -std=f95

--- Comment #2 from uttamp at us dot ibm dot com 2005-10-19 22:25 --- (In reply to comment #1) > dimag is part of the fortran 95 standard, right? > > If not this is not a bug (or really a dup another one which says that gfortran > is not constainate with other fortran co

[Bug fortran/24447] New: dimag_ undefined error with -std=f95

Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux

[Bug fortran/24337] New: Syntax error in data declaration

: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64_linux GCC host triplet: powerpc64_linux GCC target triplet: powerpc64_linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24337

[Bug fortran/24336] New: fortran variable name exceeds the maximum limit per standard

ndard Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com GCC build triplet: powerpc64_linux GCC

[Bug fortran/24110] INTERVAL: Error: Unclassifiable statement

--- Additional Comments From uttamp at us dot ibm dot com 2005-09-29 16:24 --- My apologies if INTERVAL is not a reserved keyword as part of fortran 95 standard? I thought it is part of the standard, or is it an extension to it? Please close it appropriately if this is invalid. Sorry

[Bug fortran/24110] New: INTERVAL: Error: Unclassifiable statement

Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC

[Bug middle-end/23785] 197.parser performance drop

-- What|Removed |Added CC||uttamp at us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23785

[Bug middle-end/23785] 197.parser performance drop

--- Additional Comments From uttamp at us dot ibm dot com 2005-09-21 01:13 --- With the latest (05-19-2005) mainline cvs tree, following are the benchmark numbers with and without ipa-inline patch (http://gcc.gnu.org/ml/gcc-cvs/2005-07/msg01016.html) compiled with flags "-O3 -m32

[Bug rtl-optimization/23785] New: 197.parser performance drop

er performance drop Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com

[Bug fortran/23661] New: 'print fmt' is unclassifiable statement in gfortran

Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc6

[Bug tree-optimization/23234] [4.1 Regression] ICE in verify_flow_info()

--- Additional Comments From uttamp at us dot ibm dot com 2005-08-04 17:57 --- (In reply to comment #1) > Confirmed, reduced testcase: > double func ( double a, double b, double c) > { > double y0; > if(a==0.0) { > y0 = -c/b; > return y0;

[Bug tree-optimization/23234] New: ICE in verify_flow_info()

unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: powerpc-linux GCC host triplet: powerpc-linux GCC target triplet: powerpc-linu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23234

[Bug fortran/23209] New: array shape conformance not checked

onent: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: powerpc-linux GCC host triplet: powerpc-linux GCC target triplet: powerpc-linux http://gcc.gnu.org/bug

[Bug fortran/19754] Shape conformance not checked

--- Additional Comments From uttamp at us dot ibm dot com 2005-08-02 17:20 --- (In reply to comment #7) > Fixed. Shouldn't the following test fail too with the shape conformance error message? program test integer ::a(2,2) real :: b(4,4) a=1 b=2.0 b = b + a end prog

[Bug c++/16240] [3.4/3.5 ABI Regression] g++ generates incorrect mangled name

--- Additional Comments From uttamp at us dot ibm dot com 2005-07-29 18:16 --- I belive, till g++ 3.3.4, the mangled string used have that '_' as hown by following example, template struct S { S(int i=0); }; template &s> void f13(); extern S s13; int main(vo

[Bug c++/16240] [3.4/3.5 ABI Regression] g++ generates incorrect mangled name

--- Additional Comments From uttamp at us dot ibm dot com 2005-07-28 18:10 --- (In reply to comment #15) > In comment #7 Giovanni was saying that the compiler was generating the wrong > string. The correct string is the one in the quote from the C++ ABI. The > compiler has

[Bug c++/16240] [3.4/3.5 ABI Regression] g++ generates incorrect mangled name

--- Additional Comments From uttamp at us dot ibm dot com 2005-07-27 22:48 --- (In reply to comment #7) > Agreed. This is quoted by the C++ ABI: > > void foo(char); // mangled as _Z3fooc > template struct CB; > // CB is mangled as

[Bug tree-optimization/22504] [4.1 Regression] benchmark - galgel fails at runtime with miscompare output

--- Additional Comments From uttamp at us dot ibm dot com 2005-07-26 17:27 --- Steven's patch has fixed the galgel failure. I've verified it on Powerpc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22504

[Bug tree-optimization/22560] New: internal compiler error: in create_tmp_var, at gimplify.c:368 "c++ testcase"

, at gimplify.c:368 "c++ testcase" Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at

[Bug c/22504] New: benchmark - galgel fails at runtime with miscompare output

: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org,uttamp at us dot ib

[Bug c/21774] mainline internal compiler error: verify_flow_info failed

--- Additional Comments From uttamp at us dot ibm dot com 2005-06-02 17:46 --- This bug seems to be fixed with the mainline gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21774

[Bug target/21761] [4.1 Regression] mainline gcc causing internal compiler error.

--- Additional Comments From uttamp at us dot ibm dot com 2005-06-01 23:31 --- I've verified that this bug has been fixed in mainline gcc. -- What|Removed |

[Bug c/21774] New: mainline internal compiler error: verify_flow_info failed

y_flow_info failed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com C

[Bug target/21761] [4.1 Regression] mainline gcc causing internal compiler error.

--- Additional Comments From uttamp at us dot ibm dot com 2005-05-26 18:23 --- (In reply to comment #0) > test case: > $ cat bug1.c > void f1() > { > long bit=0, exponent; > exponent = -exponent; > for (bit = 1; exponent; bit <<= 1)

[Bug c/21761] New: mainline gcc causing internal compiler error.

at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org,geoffk at gcc dot gnu dot org,uttamp at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21761