[Bug target/19566] x86_64 - inconsistent choice of parameter passing method for 16 byte struct

--- Additional Comments From aj at gcc dot gnu dot org 2005-02-19 07:06 --- Honza, could you look at this, please? -- What|Removed |Added AssignedTo|unassigned at g

[Bug preprocessor/20072] make install doesn't create /usr/local/info/dir if .../dir not already present.

-- What|Removed |Added Summary|make install doesn't create |make install doesn't create |/usr/local/info/dir .../dir |/usr/local/info/dir if

[Bug preprocessor/20072] New: make install doesn't create /usr/local/info/dir .../dir not already present.

* Cpp: (cpp). The GNU C preprocessor. install-info(/usr/local/info/cpp.info): no file /usr/local/info/dir/dir, retrieving backup file /var/ backups/infodir.bak. cp: /usr/local/info/dir/dir: No such file or directory install-info(/usr/local/info/cpp.info): copying /var/backups/infodir.bak to /usr/

[Bug middle-end/19988] [4.0 Regression] pessimizes fp multiply-add/subtract combo

--- Additional Comments From roger at eyesopen dot com 2005-02-19 05:41 --- Re: comment #5 For floating point expressions, -(A+B) is only transformed into (-A)-B or (-B)-A when the user explicitly specifies -ffast-math, i.e. only when flag_unsafe_math_optimizations is true. Re: comment

[Bug libstdc++/20071] [4.0 regression] newlib target testsuite regressions: libstdc++: tr1/6_containers/tuple

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

[Bug libstdc++/20071] New: [4.0 regression] newlib target testsuite regressions: libstdc++: tr1/6_containers/tuple

Between LAST_UPDATED: "Fri Feb 18 00:18:46 UTC 2005" and "Fri Feb 18 15:14:59 UTC 2005" these regressions were introduced on trunk for cris-axis-elf: FAIL: tr1/6_containers/tuple/comparison_operators/comparisons.cc (test for excess errors) WARNING: tr1/6_containers/tuple/comparison_operators/compa

[Bug rtl-optimization/20070] If-conversion can't match equivalent code, and cross-jumping only works for literal matches

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-19 05:04 --- Confirmed based on RTH's comments to the patch. -- What|Removed |Added Status|UN

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 04:02 --- Subject: Bug 20056 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 04:02:10 Modified files: gcc/java : ChangeLog verify-impl.c Log message

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 03:57 --- Subject: Bug 20056 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 03:57:21 Modified files: libjava: ChangeLog verify.cc Added files:

[Bug rtl-optimization/20070] If-conversion can't match equivalent code, and cross-jumping only works for literal matches

-- What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20070

[Bug other/17652] [meta-bug] GCC 4.1 pending patches

-- What|Removed |Added BugsThisDependsOn||20070 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17652

[Bug rtl-optimization/20070] New: If-conversion can't match equivalent code, and cross-jumping only works for literal matches

20050218 has been posted here: http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01066.html -- Summary: If-conversion can't match equivalent code, and cross- jumping only works for literal matches Product: gcc Version: 3.3 S

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

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

[Bug libstdc++/10606] uncaught_exception() returns false too early

-- What|Removed |Added Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10606

[Bug libstdc++/10606] uncaught_exception() returns false too early

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

[Bug libstdc++/10606] uncaught_exception() returns false too early

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 02:35 --- Subject: Bug 10606 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 02:35:25 Modified files: gcc/cp : ChangeLog except.c libstdc++

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From bonniot at users dot sf dot net 2005-02-19 02:35 --- Since bytecode classes cannot be put in the testsuite at the moment, here is a Java source that, when first compiled to bytecode, exercises this bug during the bytecode->native compilation, still with --ind

[Bug fortran/13082] Function entries and entries with alternate returns not implemented

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

[Bug fortran/20069] gfortran cannot compile ranlib

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-19 02:33 --- *** This bug has been marked as a duplicate of 13082 *** -- What|Removed |Added

[Bug fortran/20069] gfortran cannot compile ranlib

--- Additional Comments From dmitri at unm dot edu 2005-02-19 02:25 --- Created an attachment (id=8230) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8230&action=view) qrgnin.f from ranlib -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20069

[Bug fortran/20069] New: gfortran cannot compile ranlib

gfortran (gcc version 4.0.0 20050216 ) cannot compile ranlib (Library of Fortran Routines for Random Number Generation) http://lib.stat.cmu.edu/general/Utexas/ gfortran -c -fPIC -O2 -mcpu=athlon-mp -mtune=athlon-mp -pipe -mieee-fp qrgnin.f -o pic/qrgnin.o In file qrgnin.f:48 END

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From tromey at gcc dot gnu dot org 2005-02-19 01:52 --- I've checked in the fix for this. -- What|Removed |Added Status|ASSIGNED

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 01:16 --- Subject: Bug 20056 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 01:16:30 Modified files: libjava: ChangeLog link.cc verify.cc

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 01:14 --- Subject: Bug 20056 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 01:14:18 Modified files: gcc/java : ChangeLog verify-glue.c verify-impl.c

[Bug c/20043] [4.0 Regression] transparent_union doesn't allow restrict qualifier removal

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

[Bug c/20043] [4.0 Regression] transparent_union doesn't allow restrict qualifier removal

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-19 00:26 --- Subject: Bug 20043 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-19 00:26:38 Modified files: gcc: ChangeLog c-typeck.c gcc/tes

[Bug java/19810] Finally handling inconsistent when compiling to class/executable

--- Additional Comments From tromey at gcc dot gnu dot org 2005-02-19 00:19 --- I investigated this some more. The code generator for "return" looks at the finally stack to decide whether to call any finally handlers. But, the code generator for "try" has a special case when the finall

[Bug libfortran/19303] Unformatted record header is 4-bytes on 32-bit targets

--- Additional Comments From jblomqvi at cc dot hut dot fi 2005-02-18 23:42 --- Somewhat related patch here: http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01085.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19303

[Bug libfortran/20068] New: Backspace problems

For an input file containing: INITIAL_CONFIG 300 The following code will fail with a runtime error if the write statement is commented out: PROGRAM Test IMPLICIT NONE INTEGER, PARAMETER :: DP = SELECTED_REAL_KIND(15,300) REAL(DP) :: init_vel CHARACTER(40) :: Fstart OPEN(UNIT=20,F

[Bug fortran/20067] gfortran: misleading error message resolving generic subroutine

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 23:26 --- Confirmed. -- What|Removed |Added Severity|normal |minor

[Bug fortran/20067] New: gfortran: misleading error message resolving generic subroutine

Hi, the following (incorrect) code gives a misleading error message when compiling: program gfcbug24 implicit none interface foo subroutine foo_8 (a, b) real (kind(1.d0)) :: a, b end subroutine foo_8 end interface real (kind(1.d0)) :: c = 1.d0 ! gfortran gives a misleading error mes

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

-- Bug 19292 depends on bug 18977, which changed state. Bug 18977 Summary: [4.0 regression] LAPACK test xeigtsts segfaults with optimization http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18977 What|Old Value |New Value ---

[Bug fortran/5900] [g77 & gfortran] Lapack regressions since g77 2.95.2

-- Bug 5900 depends on bug 18977, which changed state. Bug 18977 Summary: [4.0 regression] LAPACK test xeigtsts segfaults with optimization http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18977 What|Old Value |New Value

[Bug tree-optimization/18977] [4.0 regression] LAPACK test xeigtsts segfaults with optimization

--- Additional Comments From wilson at gcc dot gnu dot org 2005-02-18 23:11 --- As previously noted, it was fixed by a patch from Zdenek Dvorak which had no testcase. This testcase has been added, and this bug report can be closed. -- What|Removed |

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From tromey at gcc dot gnu dot org 2005-02-18 23:10 --- There is a special case in "putfield" for setting a field before the object reference has been initialized -- this is valid in some cases. This bug occurs because we aren't properly checking all the precondi

[Bug tree-optimization/18977] [4.0 regression] LAPACK test xeigtsts segfaults with optimization

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-18 23:01 --- Subject: Bug 18977 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-18 23:01:33 Modified files: gcc/testsuite : ChangeLog Added files: gcc/t

[Bug tree-optimization/19786] [4.0 Regression] Aliasing optimisation bug

--- Additional Comments From aoliva at gcc dot gnu dot org 2005-02-18 22:53 --- Very odd... A rebuild after make clean was enough to trigger the problem. Maybe I haven't rebuilt all of libstdc++-v3 lately, but it's odd because I'd thought all of the relevant libstdc++ code was brought

[Bug fortran/20058] Error on kind 16 hex data statement

--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-18 22:48 --- I have a tentative patch for this problem. Unfortunately, it leads to a different problem. It appears that if your system supports integer(kind=16), then gfortran can't print the values.

[Bug middle-end/20066] Ordering of logical constants determines if they're correctly emitted

--- Additional Comments From tobi at gcc dot gnu dot org 2005-02-18 22:34 --- I should also add amphasis to the point that this only happens for LOGICAL constants. To see how they're defined, look at gfc_build_logical_type in fortran/trans-types.c. -- http://gcc.gnu.org/bugzilla/show

[Bug middle-end/20066] Ordering of clogical onstants determines if they're correctly emitted

--- Additional Comments From tobi at gcc dot gnu dot org 2005-02-18 22:31 --- (In reply to comment #0) > In other words, the code is correct for the former program, but not for the > latter, as here both alignment may be wrong and memory beyond the correctly > initialized space will be r

[Bug middle-end/20066] Ordering of clogical onstants determines if they're correctly emitted

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 22:30 --- Confirmed, middle-end is closer to the reality as this happens without optimization on. -- What|Removed |Added --

[Bug rtl-optimization/20066] New: Ordering of clogical onstants determines if they're correctly emitted

There's a difference between the assembly emitted for the following two Fortran tests: PRINT *, .TRUE., .TRUE_8 ; END and PRINT *, .TRUE._8, .TRUE ; END Where for the former we get .align 4 .LC1: .long 1 the latter gives: .align 8 .LC1: .long 1 .lo

[Bug fortran/19543] formated output for logical(8) variables fails

-- What|Removed |Added BugsThisDependsOn||20066 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19543

[Bug target/19886] [4.0 Regression] g++.dg/eh/registers1.C execution test fails

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 22:26 --- Fixed. -- What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug tree-optimization/20065] DOM working for _Bool but not for int

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 22:26 --- Confirmed, this is basically the same as PR 15911. -- What|Removed |Added BugsThisDependsOn

[Bug tree-optimization/20065] New: DOM working for _Bool but not for int

The the .vars dump for following functions (that only differ by the type of their parameters): void test55 (_Bool XXX, _Bool YYY) { if (XXX && YYY) { if (!XXX) link_error (); } } void test555 (int XXX, int YYY) { if (XXX && YYY) { if (!XXX) link_erro

[Bug tree-optimization/18178] Missed opportunity for removing bounds checking

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 22:01 --- Suspending as fixed and moving the target milestone to 4.1.0 so we know to retest it when tcb gets merged in. -- What|Removed |Added ---

[Bug tree-optimization/19659] GCC does not remove an "if" statement that never triggers.

-- Bug 19659 depends on bug 18178, which changed state. Bug 18178 Summary: Missed opportunity for removing bounds checking http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18178 What|Old Value |New Value --

[Bug tree-optimization/18178] Missed opportunity for removing bounds checking

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 22:00 --- (In reply to comment #7) > (In reply to comment #6) > > Fix. http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01074.html. > > For 4.0 ? No, but for 4.1, reopening as there is no 4.1 right now. --

[Bug java/20056] [4.0 regression] 'verification failed: incompatible type on stack' with --indirect-dispatch

--- Additional Comments From tromey at gcc dot gnu dot org 2005-02-18 22:00 --- I'm looking at this -- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |t

[Bug tree-optimization/18178] Missed opportunity for removing bounds checking

--- Additional Comments From schlie at comcast dot net 2005-02-18 21:57 --- (In reply to comment #6) > Fix. http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01074.html. For 4.0 ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18178

[Bug tree-optimization/19659] GCC does not remove an "if" statement that never triggers.

-- Bug 19659 depends on bug 18178, which changed state. Bug 18178 Summary: Missed opportunity for removing bounds checking http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18178 What|Old Value |New Value --

[Bug tree-optimization/18178] Missed opportunity for removing bounds checking

--- Additional Comments From dnovillo at gcc dot gnu dot org 2005-02-18 21:44 --- Fix. http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01074.html. The patch allows VRP to eliminate 42% more conditionals on cc1-i-files and 173% more conditionals on DLV. But produces little difference in

[Bug fortran/20063] n*'xxxx' disables padding

--- Additional Comments From tobi at gcc dot gnu dot org 2005-02-18 21:37 --- Well, more precisely: they're zero-padded instead of being padded with blanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20063

[Bug fortran/20063] n*'xxxx' disables padding

--- Additional Comments From tobi at gcc dot gnu dot org 2005-02-18 21:35 --- >From the generated assembly .ascii "a " .zero 4294967292 .ascii "" .zero 4 .ascii "" .zero 4 .zero 4 i.e. the elements that are

[Bug c++/20064] Types shall not be defined in casts in the strict mode.

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 21:29 --- There are two things here, -pedantic does not enable strict mode, just the warnings for strict mode, use -pedantic-errors instead. Anyways this is rejected by default with 3.4.0 and above. --

[Bug tree-optimization/18178] Missed opportunity for removing bounds checking

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-18 21:29 --- Subject: Bug 18178 CVSROOT:/cvs/gcc Module name:gcc Branch: tree-cleanup-branch Changes by: [EMAIL PROTECTED] 2005-02-18 21:28:58 Modified files: gcc: C

[Bug c++/20064] New: Types shall not be defined in casts in the strict mode.

Sourc code for t.cpp: int mymain() { void *p = (void *)(struct {int i;} *)0; /* error - can't define a type in a cast */ return 0; } Expected Behaviour: --

[Bug target/19886] [4.0 Regression] g++.dg/eh/registers1.C execution test fails

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-18 21:23 --- Subject: Bug 19886 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-18 21:23:16 Modified files: gcc: ChangeLog gcc/config/ia64: i

[Bug target/20054] [4.0 Regression] ICE in change_address_1

-- What|Removed |Added Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20054

[Bug target/20054] [4.0 Regression] ICE in change_address_1

--- Additional Comments From uweigand at gcc dot gnu dot org 2005-02-18 21:15 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/20054] [4.0 Regression] ICE in change_address_1

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-18 21:11 --- Subject: Bug 20054 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-18 21:11:07 Modified files: gcc: ChangeLog gcc/config/s390: s

[Bug fortran/20063] gfortran assembler error, n*'xxxx' is broken

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 21:07 --- (In reply to comment #1) > Your code compiles fine on amd64-*-freebsd where I'm using a gfortran > form 20050218 sources. I do get a warning though Darwin's as treats those warnings a

[Bug fortran/20063] gfortran assembler error, n*'xxxx' is broken

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 21:06 --- Confirmed, reduced to: block data blkdat character*8 names common/vfile/names(3) data names / 'a',2*''/ end -- What|Removed |Added -

[Bug fortran/20063] gfortran assembler error - : Bad Absolute Expression, absolute 0 assumed.

--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-18 21:01 --- Your code compiles fine on amd64-*-freebsd where I'm using a gfortran form 20050218 sources. I do get a warning though troutmask:kargl[205] /usr/tmp/sgk/bin/gfc -c e.f /var/tmp/ccvV0

[Bug tree-optimization/18977] [4.0 regression] LAPACK test xeigtsts segfaults with optimization

--- Additional Comments From wilson at gcc dot gnu dot org 2005-02-18 20:53 --- This is a tree-optimization problem not a target problem. -- What|Removed |Added Assi

[Bug fortran/20063] New: gfortran assembler error - : Bad Absolute Expression, absolute 0 assumed.

I get this error with the Macintosh gfortran from the 20050213 package with some of my programs. [dranta:~/tests/gfortran] dir% gfortran -c block.f /var/tmp//ccu5xNom.s:28:Bad Absolute Expression, absolute 0 assumed. /var/tmp//ccu5xNom.s:28:Repeat < 0, .space ignored /var/tmp//ccu5xNom.s:88:Bad Ab

[Bug tree-optimization/19786] [4.0 Regression] Aliasing optimisation bug

a Core 1, with a g++ which I have just built (20050218). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19786

[Bug target/19830] cris-elf testsuite failure: gcc.c-torture/execute/920501-8.c execute tests.

--- Additional Comments From hp at gcc dot gnu dot org 2005-02-18 20:32 --- One final note: this code is at the point in the simulator trace where the number of digits is calculated and first seen to be different between the faulty code and working code (that is, working due to unrelated

[Bug target/19830] cris-elf testsuite failure: gcc.c-torture/execute/920501-8.c execute tests.

--- Additional Comments From hp at gcc dot gnu dot org 2005-02-18 20:28 --- .dbr: (insn:QI 852 851 853 /home/hp/cvs_areas/combined/cvs_write/newlib/libc/stdio/vfprintf.c:1310 (set (cc0) (compare (reg/v/f:SI 2 r2 [orig:130 bp ] [130]) (reg/f:SI 9 r9 [orig:738 bp ] [73

Re: configuration problem using --enable-intermodule on x86_64-unknown-linux-gnu

Thanks, for looking into it. kenny Andrew Pinski wrote: On Feb 18, 2005, at 11:50 AM, Kenneth Zadeck wrote: The build gets partially thru the stage2 and then crashes when trying to compile most of the back end in one step with the following message: gcc: cannot specify -o with -c or -S and multip

[Bug target/19636] Can't compile ethernut OS (avr-gcc)

-- What|Removed |Added CC||berndtrog at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19636

[Bug target/19830] cris-elf testsuite failure: gcc.c-torture/execute/920501-8.c execute tests.

--- Additional Comments From hp at gcc dot gnu dot org 2005-02-18 20:25 --- Upon closer examination, the miscompiled vfprintf.c is missing a compare insn. This seems to have been the same bug as PR 19898. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19830

[Bug ada/19959] [4.0 Regression] Can't compile gnattools for the cross targets

--- Additional Comments From berndtrog at yahoo dot com 2005-02-18 20:22 --- Fails for --target=i386-elf too. -- What|Removed |Added GCC target triplet|avr

[Bug ada/18659] [4.0 Regression] ACATS ICE in bug in tree-sra.c:1507 on x86 and ppc-darwin (6 FAIL)

--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-02-18 19:20 --- > > SRA is an Ada killer because of the the abuse of VIEW_CONVERT_EXPRs by the > > Ada > > front-end. I think it should be disabled in the Ada compiler for 4.0.x. > > Sounds reasonable to me. OK, I'll

[Bug c++/19508] [4.0 regression] dwarf2, ICE on __attribute__(aligned) in class template

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 19:14 --- The ICE itself is fixed and the rest of the bug is referenced in PR 17743 so closing as fixed. -- What|Removed |Added ---

[Bug c++/19508] [4.0 regression] dwarf2, ICE on __attribute__(aligned) in class template

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-18 19:12 --- Subject: Bug 19508 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-02-18 19:11:58 Modified files: gcc/cp : ChangeLog decl2.c gcc/testsu

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From pcarlini at suse dot de 2005-02-18 19:06 --- Agreed... -- What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From arturas at inf dot unibz dot it 2005-02-18 19:04 --- Subject: Re: hash_map leak memory Hi Andrew, Thanks for the reply. I think you are correct. I overlooked that information completely. It seems there's no memory leak. I apologies for taking your time.

[Bug tree-optimization/19952] ICE: tree check: expected class 'declaration', have 'statement' (label_expr) in tree_verify_flow_info, at tree-cfg.c:3709

--- Additional Comments From dpatel at apple dot com 2005-02-18 19:02 --- Subject: Re: ICE: tree check: expected class 'declaration', have 'statement' (label_expr) in tree_verify_flow_info, at tree-cfg.c:3709 ok - Devang -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19952

[Bug ada/19140] ACATS c37402a segfaults at runtime

--- Additional Comments From uweigand at gcc dot gnu dot org 2005-02-18 19:01 --- This test case fails on s390(x) as well; in fact it is quite annoying because it causes the whole test suite to hang ... The reason for this appears to be that the Ada runtime has installed a segfault hand

[Bug target/20054] [4.0 Regression] ICE in change_address_1

--- Additional Comments From uweigand at gcc dot gnu dot org 2005-02-18 18:45 --- OK, now I see the problem: cleanup_subreg_operands *does* indeed touch only operands. However, the result of the splitter matches the *llgt_didi insn instead of *llgt_disi, because after reload nonimmediat

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From pcarlini at suse dot de 2005-02-18 18:51 --- With valgrind, I cannot reproduce the problem on 3.3.3: ==32676== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1) ==32676== malloc/free: in use at exit: 296360 bytes in 56 blocks. ==32676== malloc/

[Bug fortran/20059] internal compiler error: Segmentation Fault - For common blocks

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 18:44 --- Confirmed, but note I think this is the same as PR 19387 even though there is no ICE in that bug. -- What|Removed |Added

[Bug middle-end/20061] Certain flags generate warnings when they should not.

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 18:38 --- Confirmed. Note this flag only turns on the dumping for the tree based loop optimizators and not for the RTL based ones. -- What|Removed |Added

Re: configuration problem using --enable-intermodule on x86_64-unknown-linux-gnu

On Feb 18, 2005, at 11:50 AM, Kenneth Zadeck wrote: The build gets partially thru the stage2 and then crashes when trying to compile most of the back end in one step with the following message: gcc: cannot specify -o with -c or -S and multiple compilations This same step works fine on my pentium

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 18:31 --- Can you read and make sure that this is not the documented "leak" (I put leak in quotes because it is not a leak really). -- http://gc

[Bug c++/20060] Ambiguous MSG in array initialization when expression is not integral constant.

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 18:28 --- Fixed in 3.4.0 and above: t.cc: In function `int mymain()': t.cc:4: error: `n' cannot appear in a constant-expression -- What|Removed |Added

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From arturas at inf dot unibz dot it 2005-02-18 18:25 --- Subject: Re: hash_map leak memory Hi Pinskia, I think I made a mistake including the code. Here's the code: - a.cc - #include #include

[Bug libstdc++/20062] hash_map leak memory

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-18 18:18 --- (In reply to comment #0) > Compile the code, rerun command, I included in the description I don't see any. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20062

[Bug libstdc++/20062] hash_map leak memory

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

[Bug c++/20062] New: hash_map leak memory

hash_map implementation of g++ extensions of STL leaks memory Environment: System: Linux rose 2.6.8-2004 #2 SMP Wed Nov 24 11:15:13 CET 2004 i686 GNU/Linux Architecture: i686 host: i486-pc-linux-gnu build: i486-pc-linux-gnu target: i486-pc-linux-gnu configured with: ../src/

[Bug libstdc++/10606] uncaught_exception() returns false too early

--- Additional Comments From david dot moore at intel dot com 2005-02-18 17:56 --- As the person who has been working on similar problems in the Intel Compiler, Martin and I had some lengthy discussions about this during which he convinced me he was correct. The result was issue 475 i

[Bug tree-optimization/19786] [4.0 Regression] Aliasing optimisation bug

--- Additional Comments From aoliva at gcc dot gnu dot org 2005-02-18 17:45 --- I can't duplicate this with a tree updated some time earlier today. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19786

[Bug target/20054] [4.0 Regression] ICE in change_address_1

--- Additional Comments From uweigand at gcc dot gnu dot org 2005-02-18 17:42 --- I think the middle-end *should* allow back-ends to use SUBREGs in that way. cleanup_subreg_operands should really act only on SUBREGs that are part of an operand, and not on SUBREGs that are part of the i

[Bug c/20061] New: Certain flags generate warnings when they should not.

I am interested in looking at the GCC loop optimization. There are some tree dump flags that are registered (via register_dump_files() in tree-optimize.c). In particular, -fdump-tree-loopinit-raw and -fdump-tree-loopdone-raw that generate warnings when they should not. Specifically: gcc -O3 -S

[Bug target/20054] [4.0 Regression] ICE in change_address_1

--- Additional Comments From jakub at gcc dot gnu dot org 2005-02-18 17:33 --- I think the reason why this paradoxical subreg of memory survived post reload is that the subreg is hardcoded in the llgt_sidi/llgt_sidi_split patterns. All other patterns have explicit subreg only around regi

[Bug c++/20060] New: Ambiguous MSG in array initialization when expression is not integral constant.

Sourc code for t.cpp: int mymain() { int n = 10; int (*p)[] = new int [2][n]; // error - 2nd dimension not constant return 0; } Expected Behaviour: -

configuration problem using --enable-intermodule on x86_64-unknown-linux-gnu

The build gets partially thru the stage2 and then crashes when trying to compile most of the back end in one step with the following message: gcc: cannot specify -o with -c or -S and multiple compilations This same step works fine on my pentium (suse 9.2) and darwin machines. I am compiling aga

[Bug java/18362] internal compiler error: in size_binop, at fold-const.c:1598

-- What|Removed |Added CC||bonniot at users dot sf dot ||net http://gcc.gnu.org/bugzilla/s

  1   2   >