[Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread ebotcazou at gcc dot gnu dot org
--- Comment #7 from ebotcazou at gcc dot gnu dot org 2006-12-23 08:05 --- > Here's the output of g++ -v if it helps: Thanks, but we still need the preprocessed sources... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30280

[Bug c/30282] New: Optimization flag -O2 generate error stack operating code

2006-12-23 Thread chenkb at ruijie dot com dot cn
Stack operating code that generated by gcc have an error. In some operating system that saved the thread's context in stack when schedule, it will be have critical problem. Enabling the compiler optimalisation (-O2 option) the error will be occuring, and don't occur when using option -O1 or -O0.

[Bug target/30282] Optimization flag -O2 generate error stack operating code

2006-12-23 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|major |normal Component|c |target http:

[Bug target/30282] Optimization flag -O1 -fschedule-insns2 cause red zone to be used when there is none

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-23 10:31 --- For 4.0 and above your sample code works but that is a different issue. Here is a testcase which fails for 4.0 and above: int find_num(int i) { int arr[5] = {0, 1, 2, 3, 4}; return arr[i]; } The problem

[Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread gdr at integrable-solutions dot net
--- Comment #8 from gdr at integrable-solutions dot net 2006-12-23 11:17 --- Subject: Re: SIGSEGV on operator==(valarray, bool) "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: | What target is this one, all I get is: | t.cc:8: error: cannot convert 'std::_Expr > >, | boo

[Bug c++/30281] [reject valid?] type deduction fails.

2006-12-23 Thread pluto at agmk dot net
--- Comment #1 from pluto at agmk dot net 2006-12-23 11:21 --- wrapper< my_error >().add_method< char const* >( &my_error::what ); such call compiles, so it looks like type deduction failure. -- pluto at agmk dot net changed: What|Removed |Added -

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread steven at gcc dot gnu dot org
-- steven at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfir

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #1 from steven at gcc dot gnu dot org 2006-12-23 12:19 --- This is what g77 outputs for this test case: results in:ackslash results in: \backslash ackslash now results inackslash \backslash now results in \backslash -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30278

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #2 from steven at gcc dot gnu dot org 2006-12-23 12:42 --- I suspect that the problem is some difference between the front end and library FORMAT parsers. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30278

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #3 from steven at gcc dot gnu dot org 2006-12-23 12:52 --- This not-for-including patch shows that we should match "\\" in io.c and treat it as a single '\\' character. This is what g77 appears to do, too. Index: io.c

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread tobi at gcc dot gnu dot org
--- Comment #4 from tobi at gcc dot gnu dot org 2006-12-23 13:12 --- NB The whole of \-ed symbols would have to be interpreted, conditionalized on -fbackslash. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30278

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #5 from steven at gcc dot gnu dot org 2006-12-23 13:17 --- Created an attachment (id=12838) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12838&action=view) Handle escaped characters if flag_backslash Slightly less horrible patch... -- http://gcc.gnu.org/bugzilla/

[Bug tree-optimization/30089] Compiling FreeFem3d uses unreasonable amount of time and memory

2006-12-23 Thread hubicka at gcc dot gnu dot org
--- Comment #13 from hubicka at gcc dot gnu dot org 2006-12-23 14:26 --- Note that we've got another noticeable jump in memory consumption today (well at least it would be very important jump if we used just 28MB of memory for aliasing :). Is that also aliasing or shall be analyzed? H

[Bug tree-optimization/30089] Compiling FreeFem3d uses unreasonable amount of time and memory

2006-12-23 Thread hubicka at gcc dot gnu dot org
--- Comment #14 from hubicka at gcc dot gnu dot org 2006-12-23 14:27 --- Well, actually the testcase now runs out of memory and ICE... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30089

[Bug fortran/30276] gfortran include problem

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #2 from steven at gcc dot gnu dot org 2006-12-23 14:48 --- I think the proper fix is to add "." to the search list of directories where include files may live. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30276

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-23 Thread steven at gcc dot gnu dot org
--- Comment #43 from steven at gcc dot gnu dot org 2006-12-23 14:51 --- Fixed in GCC 4.3.0 -- steven at gcc dot gnu dot org changed: What|Removed |Added Statu

[Bug tree-optimization/30089] Compiling FreeFem3d uses unreasonable amount of time and memory

2006-12-23 Thread dberlin at dberlin dot org
--- Comment #15 from dberlin at gcc dot gnu dot org 2006-12-23 16:21 --- Subject: Re: Compiling FreeFem3d uses unreasonable amount of time and memory On 23 Dec 2006 14:26:00 -, hubicka at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote: > > > --- Comment #13 from hubicka at gcc

[Bug middle-end/7651] Define -Wextra strictly in terms of other warning flags

2006-12-23 Thread manu at gcc dot gnu dot org
--- Comment #11 from manu at gcc dot gnu dot org 2006-12-23 17:45 --- Subject: Bug 7651 Author: manu Date: Sat Dec 23 17:45:33 2006 New Revision: 120173 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120173 Log: 2006-12-23 Manuel Lopez-Ibanez <[EMAIL PROTECTED]> PR mi

[Bug target/29867] [4.3 Regression] building libgfortran fails because of multiple definitions gcc-4.3-20061111

2006-12-23 Thread dfranke at gcc dot gnu dot org
--- Comment #17 from dfranke at gcc dot gnu dot org 2006-12-23 17:53 --- Created an attachment (id=12839) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12839&action=view) fixincludes: find headers in distro-specfic paths * fixincl.c(fix_applies): Use fnmatch instead of strstr to

Re: [Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread Andrew Pinski
On Sat, 2006-12-23 at 11:17 +, gdr at integrable-solutions dot net wrote: > > I don't remember I ever used this funky __builtin_expect. > valarray is improving everyday :-( You most likely did not but assert did :). -- Pinski

[Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread pinskia at gmail dot com
--- Comment #9 from pinskia at gmail dot com 2006-12-23 18:50 --- Subject: Re: SIGSEGV on operator==(valarray, bool) On Sat, 2006-12-23 at 11:17 +, gdr at integrable-solutions dot net wrote: > > I don't remember I ever used this funky __builtin_expect. > valarray is impr

[Bug fortran/30283] New: Specification expression not properly recognized in type declaration

2006-12-23 Thread anlauf at gmx dot de
Hi, the following legal code fails to compile with gfortran: % cat gfcbug50.f90 module gfcbug50 implicit none contains subroutine foo (n, y) integer, intent(in) :: n integer, dimension(bar (n)) :: y ! Array bound is specification expression, which is allowed (F2003, sect.

[Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread sebor at roguewave dot com
--- Comment #10 from sebor at roguewave dot com 2006-12-23 20:46 --- Created an attachment (id=12840) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12840&action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30280

[Bug fortran/30284] New: ICE in gfc_add_modify, at fortran/trans.c:159

2006-12-23 Thread anlauf at gmx dot de
Hi, here's another one: % cat gfcbug51.f90 program gfcbug51 implicit none type date_t character(len=12) :: date = '200612231200' ! mmddhhmm end type date_t type year_t integer :: year = 0 end type year_t type(date_t) :: file(1) type(year_t) :: time(1) read (file% d

[Bug target/28764] [4.2 Regression] libjava build failure on sh4

2006-12-23 Thread ubizjak at gmail dot com
--- Comment #18 from ubizjak at gmail dot com 2006-12-23 21:24 --- (In reply to comment #12) > As far as I can see, the i387 mode switching is already completely broken, > because it treats the different modes of a single mode-switchable entity > as separate entities. NO, it is _NOT_ b

[Bug fortran/30285] New: gfortran huge (excessive?) memory usage with large modules

2006-12-23 Thread anlauf at gmx dot de
Hi, gfortran seems to use much more memory at compile time when I "use" larger modules that contain many symbols, even if I "use, only" selected one. In the described situation it needs significantly more memory than "competitors". The attached archive contains the following main program and thr

[Bug fortran/30285] gfortran huge (excessive?) memory usage with large modules

2006-12-23 Thread anlauf at gmx dot de
--- Comment #1 from anlauf at gmx dot de 2006-12-24 00:28 --- Created an attachment (id=12841) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12841&action=view) main.f90 + 3 modules included my main -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30285

[Bug fortran/30278] Inconsistencies with backslash handling

2006-12-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-12-24 03:14 --- With th patch in comment #5, NIST tests go OK. It matches g77 behavior. I am thinking though that the default behavior should be -fno-backslash. With -fno-backslash, gfortran matches intel behavior. My impress

[Bug middle-end/30250] Evaluate lgamma/gamma at compile-time

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 03:33 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCON

[Bug middle-end/30251] Evaluate bessel functions at compile-time

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 03:34 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCON

[Bug target/30266] [4.1 Regression] Segfault with -O2 -ftrapv

2006-12-23 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Keywords||ice-on-valid-code Known to fail||4.1

[Bug middle-end/30286] New: [4.1 Regression] Segfault with -O2 -ftrapv

2006-12-23 Thread pinskia at gcc dot gnu dot org
Testcase: struct free_block { struct free_block *next; }; struct mm { struct free_block *free_arr[25]; }; void get_exact(int i, struct mm *mm, struct free_block *p) { int j; for (j=14; j>i; j--) mm->free_arr[j] = p->next; } -- Summary: [4.1 Regression] Segfault with -O2

[Bug target/30266] [4.1 Regression] Segfault with -O2 -ftrapv

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-24 04:40 --- *** This bug has been marked as a duplicate of 30286 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added --

[Bug middle-end/30286] [4.1 Regression] Segfault with -O2 -ftrapv

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 04:40 --- *** Bug 30266 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug middle-end/30286] [4.1 Regression] Segfault with -O2 -ftrapv

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-24 04:41 --- Confirmed, I created a new bug because the other one was a mess since the preprocessed source was not attached but just pasted. -- pinskia at gcc dot gnu dot org changed: What|Removed

[Bug target/30153] -fPIC failure

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 04:49 --- As far as I can tell this is really a binutils issue. the difference between static inline and just static is where foo is emitted. In the static inline case, it is emitted after bar. -- http://gcc.gnu.org/bugz

[Bug c/30171] non-portable va_list abuse should be diagnostic

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-24 04:50 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCON

[Bug libstdc++/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-12-24 04:56 --- So on solaris assert is defined as (void)((operand) || (__assert (),0) ); -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30280

[Bug target/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #12 from pinskia at gcc dot gnu dot org 2006-12-24 05:02 --- I am starting to think Solaris's definition of assert is incorrect because you can actually overload "operator ||" and force evulation of both operands in C++ which is what is happening here. All other asserts I k

[Bug fortran/30207] [4.2 Regression] ICE in gfc_dep_resolver with where (a < 0) a(:) = 1

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-12-24 05:03 --- Fixed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|REOPENE

[Bug driver/17621] Add option to have GCC not search $(prefix)

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #19 from pinskia at gcc dot gnu dot org 2006-12-24 05:04 --- Fixed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug target/24036] [4.1/4.2 Regression] [e500] ICE in subreg_offset_representable_p, at rtlanal.c:3143

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-12-24 05:08 --- Fixed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug fortran/30145] Fortran 90: write statement fails to ignore zero-sized array...

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #10 from pinskia at gcc dot gnu dot org 2006-12-24 05:09 --- Fixed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNE

[Bug middle-end/30229] Out of memory error during make of gcc 4.1.1 using 3.3.5

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 05:11 --- Try first compiling 4.0.0 and then 4.1.1 since it is the compiler which installed already which is running out of memory. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30229

[Bug target/30280] SIGSEGV on operator==(valarray, bool)

2006-12-23 Thread gdr at integrable-solutions dot net
--- Comment #13 from gdr at integrable-solutions dot net 2006-12-24 05:23 --- Subject: Re: SIGSEGV on operator==(valarray, bool) "pinskia at gmail dot com" <[EMAIL PROTECTED]> writes: | --- Comment #9 from pinskia at gmail dot com 2006-12-23 18:50 --- | Subject: Re: SIGSEGV

[Bug fortran/30284] ICE in gfc_add_modify with internal reads

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 05:25 --- Reduced testcase: program gfcbug51 type date_t character(len=12) :: date end type date_t type(date_t) :: file(1) read (file%date(1:4),'(i4)') a end program gfcbug51 -- Here is

[Bug fortran/30249] Pointers not given target type in GFORTRAN

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 05:36 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added OtherBugsDependingO|

[Bug c++/30158] [4.0/4.1/4.2/4.3 regression] ICE with invalid statement-expressions

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-24 06:12 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|norma

[Bug tree-optimization/30177] [4.3 Regression] ICE in ssa_operand_alloc, at tree-ssa-operands.c:365

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-24 06:13 --- I think this has been fixed already. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30177

[Bug bootstrap/19176] [4.0/4.1/4.2/4.3 Regression] static gcc cannot be build (libgcc_eh.a required for static gcc)

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-24 06:21 --- *** This bug has been marked as a duplicate of 26510 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added --

[Bug target/26510] [4.1/4.2/4.3 Regression] --disable-shared broken for darwin platform

2006-12-23 Thread pinskia at gcc dot gnu dot org
--- Comment #9 from pinskia at gcc dot gnu dot org 2006-12-24 06:21 --- *** Bug 19176 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---