[Bug tree-optimization/31703] [4.3 regression]: Gcc 4.3 revision 124101 failed to compile gcc 3.2

2007-04-25 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Component|rtl-optimization|tree-optimization Keywords|

[Bug libfortran/31706] recl specified for unformatted sequential file does not work

2007-04-25 Thread gcc-bugs at wbfb dot de
--- Comment #2 from gcc-bugs at wbfb dot de 2007-04-25 22:16 --- (In reply to comment #1) What is your gfortran version (gfortran -v)? I cannot repoduce it with neither -static nor without using gfortran 4.1.3 20070413 (prerelease) and 4.3.0 20070425 (experimental) under x86_64

[Bug libfortran/31706] recl specified for unformatted sequential file does not work

2007-04-25 Thread tkoenig at gcc dot gnu dot org
--- Comment #3 from tkoenig at gcc dot gnu dot org 2007-04-25 22:39 --- This is PR 31099, fixed on more recent versions of gfortran. Closing. *** This bug has been marked as a duplicate of 31099 *** -- tkoenig at gcc dot gnu dot org changed: What|Removed

[Bug libfortran/31099] [4.3/4.2 regression] Runtime error on legal code using RECL

2007-04-25 Thread tkoenig at gcc dot gnu dot org
--- Comment #20 from tkoenig at gcc dot gnu dot org 2007-04-25 22:39 --- *** Bug 31706 has been marked as a duplicate of this bug. *** -- tkoenig at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31696] -malign-double trashes fortran format

2007-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #5 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-25 22:46 --- I guess I walk away from you guys at this point. You need to think carefully about the fortran standard, which does not define any abi whatsoever (unfortunately). The fortran programmer is not supposed to think

[Bug fortran/31696] -malign-double trashes fortran format

2007-04-25 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-04-25 22:58 --- Yes the fortran standard does not define the ABI, the target which you are compiling for does and if you change it in any way (which is what options like -malign-double does) you are going to run into problems like

[Bug c/31707] New: Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread hackbunny at reactos dot com
Command line: gcc -c lib\rtl\workitem.c -o obj-i386\lib\rtl\workitem.o -Iobj-i386\lib\rtl -Ilib\rtl -D__USE_W32API -D_NTOSKRNL_ -D__NO_CTYPE_INLINES -DNO_RTL_INLINES -D_NTSYSTEM_ -D_NTDLLBUILD_ -Iobj-i386\lib\rtl -I. -Iinclude -Iinclude\psdk -Iinclude\crt -Iinclude\ddk -Iinclude\GL -Iinclude\ndk

[Bug c/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread hackbunny at reactos dot com
--- Comment #1 from hackbunny at reactos dot com 2007-04-25 23:28 --- Created an attachment (id=13442) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13442action=view) Preprocessor output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707

[Bug c/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread hackbunny at reactos dot com
--- Comment #2 from hackbunny at reactos dot com 2007-04-25 23:29 --- Created an attachment (id=13443) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13443action=view) GIMPLE source for the test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707

[Bug c/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread hackbunny at reactos dot com
--- Comment #3 from hackbunny at reactos dot com 2007-04-25 23:30 --- Created an attachment (id=13444) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13444action=view) Final tree dump for the test case By going through the tree dump, it appears the warning has no reason to be --

[Bug c/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread hackbunny at reactos dot com
--- Comment #4 from hackbunny at reactos dot com 2007-04-25 23:33 --- A couple more notes: * no warning if setjmp is used instead of __builtin_setjmp * no warning if the call to bar() is removed * no warning in GCC 4.1.2 -- hackbunny at reactos dot com changed: What

[Bug middle-end/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp

2007-04-25 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|major |normal Component|c |middle-end

[Bug middle-end/31707] Spurious 'variable' may be used uninitialized in this function warnings when using __builtin_setjmp and loops and extern function call

2007-04-25 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-04-25 23:59 --- The problem is that the CFG does not know that the first time through the loop when calling bar, you cannot get to the setjmp. This is a hard problem to solve really. You have to track the uninitialized variable

[Bug libmudflap/31681] [4.3 regression]: Many libmudflap faulures

2007-04-25 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31681

[Bug tree-optimization/31703] [4.3 regression]: Gcc 4.3 revision 124101 failed to compile gcc 3.2

2007-04-25 Thread sje at cup dot hp dot com
--- Comment #4 from sje at cup dot hp dot com 2007-04-26 00:58 --- The patch mentioned in Comment #2 is also causing problems on IA64 Linux and HP-UX. If I build a bootstrap compiler and then use the resulting fortran compiler to compile the SPEC 2006 benchmark 173.applu the resulting

[Bug c++/31708] New: threadprivate with function block static reports incomplete type

2007-04-25 Thread mstaley at lanl dot gov
Yesterday (2007-4-25) I downloaded gcc 4.2 and ran into a problem with g++ as illustrated here: templateclass T struct xyz { T x, y, z; }; templateclass T struct myclass { void fun(void); }; templateclass T void myclassT::fun(void) {

[Bug target/31403] wrong branch instructions generated with -m2a on sh-elf

2007-04-25 Thread kkojima at gcc dot gnu dot org
--- Comment #6 from kkojima at gcc dot gnu dot org 2007-04-26 01:30 --- Subject: Bug 31403 Author: kkojima Date: Thu Apr 26 01:29:54 2007 New Revision: 124171 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=124171 Log: PR target/31403 * config/sh/sh.md (movsi_ie):

[Bug rtl-optimization/31686] wrong codegen from reload

2007-04-25 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-26 01:55 --- Fixed: http://gcc.gnu.org/ml/gcc-cvs/2007-04/msg00727.html -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/28675] [4.1/4.2/4.3 regression] ICE in extract_insn, at recog.c:2084 (unrecognizable insn) [arm]

2007-04-25 Thread ian at airs dot com
--- Comment #13 from ian at airs dot com 2007-04-26 02:01 --- Created an attachment (id=13445) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13445action=view) Proposed patch I'm testing this patch on i686-pc-linux-gnu. If somebody can test it on ARM, that would be great. --

[Bug target/30052] [4.2 Regression] possible quadratic behaviour.

2007-04-25 Thread dberlin at dberlin dot org
--- Comment #16 from dberlin at gcc dot gnu dot org 2007-04-26 02:20 --- Subject: Re: [4.2 Regression] possible quadratic behaviour. On 25 Apr 2007 20:56:24 -, pluto at agmk dot net [EMAIL PROTECTED] wrote: --- Comment #15 from pluto at agmk dot net 2007-04-25 21:56

[Bug pending/31709] New: combine and __attributes__((__packed__)) conflict.

2007-04-25 Thread matt at 3am-software dot com
a.c: struct f { int i; } __attribute__((__packed__)); const char *foo(struct f *); b.c: struct f; const char *foo(struct f *); c.c (identical to a.c): struct f { int i; } __attribute__((__packed__)); const char *foo(struct f *); gcc -fsyntax-only -combine -ffreestanding a.c b.c c.c

[Bug target/31388] ICE building libiberty multilib for mips16 multilibs

2007-04-25 Thread mmitchel at gcc dot gnu dot org
--- Comment #3 from mmitchel at gcc dot gnu dot org 2007-04-26 03:29 --- Subject: Bug 31388 Author: mmitchel Date: Thu Apr 26 03:29:43 2007 New Revision: 124172 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=124172 Log: PR c++/31388 * cp-tree.h (ARITHMETIC_TYPE):

[Bug c++/31338] [4.1/4.2/4.3 regression] Cannot apply ! to complex constants

2007-04-25 Thread mmitchel at gcc dot gnu dot org
--- Comment #4 from mmitchel at gcc dot gnu dot org 2007-04-26 03:37 --- Subject: Bug 31338 Author: mmitchel Date: Thu Apr 26 03:37:20 2007 New Revision: 124173 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=124173 Log: Fix PR# in ChangeLog: PR c++/31338 *

[Bug c++/31338] [4.1/4.2 regression] Cannot apply ! to complex constants

2007-04-25 Thread mmitchel at gcc dot gnu dot org
--- Comment #5 from mmitchel at gcc dot gnu dot org 2007-04-26 03:37 --- Fixed in 4.3.0. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31683] bogus warnings with optional arguments

2007-04-25 Thread jv244 at cam dot ac dot uk
--- Comment #7 from jv244 at cam dot ac dot uk 2007-04-26 05:54 --- (In reply to comment #6) Regarding the original problem with CP2k: A dependence on the optimization options usually indicates a middle-end problem rather than a (Fortran) front-end problem. As it occurred around the

<    1   2