[Bug c++/31584] ICE on probably invalid code

--- Comment #3 from numerical dot simulation at web dot de 2007-04-18 07:51 --- I started a discussion about this code on comp.lang.c++.moderated, subject "enum in template memfun in class template - valid C++?" see

[Bug c++/31617] [4.3 Regression] Segfault in integer_zerop, called via ipa-type-escape.c

--- Comment #4 from tbm at cyrius dot com 2007-04-18 07:39 --- Olga Golovanevsky <[EMAIL PROTECTED]> made some changes to that part of the compiler during this period. Added to CC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31617

[Bug c++/31617] [4.3 Regression] Segfault in integer_zerop, called via ipa-type-escape.c

--- Comment #3 from tbm at cyrius dot com 2007-04-18 07:37 --- Works with 4.3 20070303 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31617

[Bug c++/31617] [4.3 Regression] Segfault in integer_zerop, called via ipa-type-escape.c

--- Comment #2 from tbm at cyrius dot com 2007-04-18 07:30 --- I should mention that you need -O2 to see this. I've confirmed the segfault on x86_64 and ia64. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31617

[Bug c++/31617] [4.3 Regression] Segfault in integer_zerop, called via ipa-type-escape.c

--- Comment #1 from tbm at cyrius dot com 2007-04-18 07:27 --- Created an attachment (id=13388) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13388&action=view) testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31617

[Bug c++/31617] New: [4.3 Regression] Segfault in integer_zerop, called via ipa-type-escape.c

I get the following segfault with gcc 4.3 20070326 and 20070417. It works with gcc 4.2: Analyzing compilation unit Performing interprocedural optimizations Program received signal SIGSEGV, Segmentation fault. integer_zerop (expr=0x0) at /home/tbm/scratch/gcc/gcc/tree.c:1295 1295

[Bug fortran/30792] DATA implied-do substring allowed with -std=f95/f2003

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31592] Better message if using non-intrinsic initialization expression

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/27589] Add compiler flag to check for uninitalized values at runtime

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31600] Better error message for redeclation of USEd symbols

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31612] -fsyntax-only documentation is not accurate

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31393] [meta-bug] gfortran compile-time problems with intrinsics

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31392] [meta-bug] gfortran problems with initialization

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31461] warn about entities in USE, ONLY statement not later used

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31447] set intent(out) arguments to uninitialized

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/28105] Check for memory allocations bigger than size_t

--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-04-18 07:05 --- (In reply to comment #1) > Will this be appropriate for all front-ends? Then, this is a duplicate of (or > very related to) bug 18063. We probably want runtime checks generated by the Fortran front-end for this c

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

--- Comment #2 from ghazi at gcc dot gnu dot org 2007-04-18 07:05 --- Created an attachment (id=13387) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13387&action=view) Dump file using -fdump-tree-vect-details Created dump file using -fdump-tree-vect-details -- http://gcc.gnu.

[Bug fortran/31610] ICE with transfer, merge in gfc_conv_expr_descriptor

--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-04-18 07:03 --- g95: string = transfer(merge (transfer(achar (ichar('A')), "x", len(string)), st 1 Error: MERGE intrinsic at (1) has different character lengths Sun: string = transfer

[Bug fortran/31547] Document when CPP is called and document the f95-cpp-input option

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/29697] gfortran should use TYPE_QUAL_CONST etc.

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/29697] gfortran should use TYPE_QUAL_CONST etc.

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29697

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

--- Comment #2 from ghazi at gcc dot gnu dot org 2007-04-18 06:58 --- (In reply to comment #1) > Try changing: > call abort() > to: > print *, msg > This will then print the error messages instead of aborting and you may be > able > to see what is going on. If I make your suggested ch

[Bug fortran/31244] data initialization with more than 2**32 elements

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31139] sum(w_re(1:nn,1)*fi(i(1:nn, ii))) up to 3.5x slower than C version

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31463] gfortran prints no warning message when an unset return value is an array

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement Status|UNCONFIRMED |NEW

[Bug fortran/31207] [4.2.1 only] advance="no" and tabs

--- Comment #10 from fxcoudert at gcc dot gnu dot org 2007-04-18 06:46 --- Created an attachment (id=13386) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13386&action=view) Output of different versions of gfortran -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31207

[Bug libfortran/31409] [4.1 only, regression] Reading after ERROR_SHORT_RECORD

--- Comment #4 from fxcoudert at gcc dot gnu dot org 2007-04-18 06:45 --- (In reply to comment #3) > Gfortran behavior matches ifort. It would be interesting to see what other > compilers do. Sun does the same as gfortran and Intel. > I have not checked gfortran 4.2 yet. However, re

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

--- Comment #1 from dorit at il dot ibm dot com 2007-04-18 06:42 --- could you please provide the .vect dump file, as generated with -fdump-tree-vect-details? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31615

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon

[Bug c++/29365] Unnecessary anonymous namespace warnings

--- Comment #19 from gcc at user dot lysator dot liu dot se 2007-04-18 06:24 --- Subject: Re: Unnecessary anonymous namespace warnings Yes, the latest patch seems to solve the problem with the ICE for me as well. Thanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29365

[Bug libfortran/31501] libgfortran internal unit I/O performance issues

--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-04-18 06:12 --- Looking at sf_read in transfer.c, we can see that we are reading one character at a time with internal units. This was done for external units because we can not anticipate where the end of the file is until we h

[Bug libfortran/31607] CALL SYSTEM produces garbled output when writing to a buffered file

--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-04-18 06:03 --- I can confirm this behavior. Putting a flush(6) before the call fixes this, so it is within the language to handle this. I am marking this as minor and I will get to it after a few other things I need to get don

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:48 --- This could be as simple as the error messages returned by the OS don't match what we put in the test case. Try changing: call abort() to: print *, msg This will then print the error messages instead of aborti

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #17 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:42 --- Will not fix on 4.1. Fixed on 4.2 and 4.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31616] New: testsuite failures in gfortran.dg/open_errors.f90

I'm getting testsuite failures in gfortran.dg/open_errors.f90 with mainline on sparc-sun-solaris2.10: http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg00897.html The logfile only says: FAIL: gfortran.dg/open_errors.f90 -O0 execution test at all optimization levels. Running it by hand, it sim

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #16 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:37 --- Subject: Bug 31366 Author: jvdelisle Date: Wed Apr 18 05:37:12 2007 New Revision: 123941 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123941 Log: 2007-04-17 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #15 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:35 --- Subject: Bug 31366 Author: jvdelisle Date: Wed Apr 18 05:35:41 2007 New Revision: 123940 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123940 Log: 2007-04-17 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/31615] New: testsuite failure in gfortran.dg/vect/vect-5.f90

I'm getting a testsuite failure in gfortran.dg/vect/vect-5.f90 with GCC trunk on sparc-sun-solaris2.10: http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg00897.html The logfile says: FAIL: gfortran.dg/vect/vect-5.f90 -O scan-tree-dump-times Alignment of access forced using versioning. 3 Running

[Bug fortran/31207] [4.2.1 only] advance="no" and tabs

--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:25 --- Its not a regression, but I would like to keep track of this for 4.2.1 along with 31051 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/31409] [4.1 4.2 regression] Reading after ERROR_SHORT_RECORD

-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31409

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #14 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:01 --- This one is a regression against g77. 4.1 fails as well. It passes the .f version of the test case with g77. I will backport to 4.2 and 4.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31366

[Bug c++/31513] [4.3 Regression] Miscompilation of Function Passing Bit Field Value to Function

--- Comment #8 from mmitchel at gcc dot gnu dot org 2007-04-18 04:44 --- Fixed in 4.3.0. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Stat

[Bug c++/31513] [4.3 Regression] Miscompilation of Function Passing Bit Field Value to Function

--- Comment #7 from mmitchel at gcc dot gnu dot org 2007-04-18 04:36 --- Subject: Bug 31513 Author: mmitchel Date: Wed Apr 18 04:36:18 2007 New Revision: 123939 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123939 Log: PR c++/31513 * call.c (convert_for_arg_pas

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-04-18 04:00 --- I believe this was a regression against 4.1. It was introduced by the record marker patch. I need to build latest 4.1 and test. I will report here teh results. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?

[Bug fortran/31614] Inability to read ascii text with generic 'f' format

--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-04-18 03:44 --- I think you should just use read(10,*) or better yet, read the whole line into a single string and search for the "=" in the string, noting the_position, then use read(stringname(the_position:),*) input list In o

[Bug testsuite/31589] gcc.dg/vect failures due to missing target specifiers

--- Comment #3 from tprince at computer dot org 2007-04-18 02:21 --- The patch which Dorit proposed does change the FAIL in the testsuite case vect-reduc-dot-u16a.c to XFAIL, according to my test. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31589

[Bug tree-optimization/31606] [4.3 Regression] ICE in try_instantiate_multiple_fields, at tree-sra.c:1601

--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-18 00:42 --- We try to get a type for size of 128bits which is TImode. And on x86, TImode is not supported. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31606

[Bug fortran/31614] New: Inability to read ascii text with generic 'f' format

I have a text file that I want to read, consisting of some text, integers and floats. I'm not able to get the code to compile without exactly specifying the width and number of decimal places for the ints and floats. Ideally, I would like to be able to write a line of code like: read(10,'(10x, f,

[Bug c++/21612] Strange symbols printed all over the error messages

--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-18 00:15 --- *** Bug 31613 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug c/31613] Meaningless error messages

--- Comment #5 from pinskia at gcc dot gnu dot org 2007-04-18 00:15 --- To mark as a dup of bug 21612. *** This bug has been marked as a duplicate of 21612 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug c/31613] Meaningless error messages

--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-18 00:14 --- Reopening to ... -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug c/31613] Meaningless error messages

--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-18 00:14 --- Reopening to ... -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #11 from Catherine dot M dot Moroney at jpl dot nasa dot gov 2007-04-18 00:12 --- Subject: Re: UBOUND as initialization expression (lacking simplification) Well, thank-you for the quick turnaround on this patch! Francois - good luck on your thesis! I remember the struggl

[Bug tree-optimization/31606] [4.3 Regression] ICE in try_instantiate_multiple_fields, at tree-sra.c:1601

-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfi

[Bug c/31613] Meaningless error messages

--- Comment #2 from agbrowne at btinternet dot com 2007-04-18 00:09 --- This is associated with the UTF-8 problem in bug no: 21612 -- agbrowne at btinternet dot com changed: What|Removed |Added --

[Bug tree-optimization/31606] [4.3 Regression] ICE in try_instantiate_multiple_fields, at tree-sra.c:1601

--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-18 00:09 --- Reduced testcase: class Collision { int edge; int triangle; float _M_instance[3] __attribute__((__aligned__)); }; void get_collisions(Collision a) { Collision b = a; } -- pinskia at gcc dot gnu dot org

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #10 from fxcoudert at gcc dot gnu dot org 2007-04-18 00:08 --- Created an attachment (id=13385) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13385&action=view) Better patch -- fxcoudert at gcc dot gnu dot org changed: What|Removed

[Bug c/31613] Meaningless error messages

--- Comment #1 from agbrowne at btinternet dot com 2007-04-17 23:56 --- I am using the standard Fedora Core 6 build with the gcc compiler supplied as part of the dist -- agbrowne at btinternet dot com changed: What|Removed |Added --

[Bug c/31613] New: Meaningless error messages

Almost all error and warning messages consist of just one character -- â (A cicumflex) This can be produced by the sample source file listed below:- int main() { int variable; } Compiled with:- % gcc -Wall file.c Gives the output:- test.c: In function â: test.c:3: warning: unused variable

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-04-17 23:51 --- Created an attachment (id=13384) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13384&action=view) Patch to fix this PR This patch should take care of the simplification. It hasn't been fully tested yet, but

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-04-17 23:22 --- (In reply to comment #6) > So, are you saying that LBOUND and UBOUND without the dimension > specifiers do not work at all? I'm saying that gfortran is missing the piece of code that allows is to use UBOUND and L

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #6 from Catherine dot M dot Moroney at jpl dot nasa dot gov 2007-04-17 23:09 --- Subject: Re: UBOUND as initialization expression (lacking simplification) So, are you saying that LBOUND and UBOUND without the dimension specifiers do not work at all? Take the attached shor

[Bug fortran/31591] UBOUND as initialization expression (lacking simplification)

--- Comment #5 from fxcoudert at gcc dot gnu dot org 2007-04-17 22:48 --- (In reply to comment #4) > By the way, the scalar version, i.e. removing "dimension" and using > "ubound(TCg_coef,1)", works. Hum, I know that one (although I never thought it would trigger a bug when I encounter

[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-04-17 22:41 --- (In reply to comment #1) > We can "fix" this (cosmetic fix for valgrind, really) by > setting sstride[0] to an arbitray value that would cause > a segfault if the value was actually used for anything. I'd go for

[Bug libfortran/31286] cshift uses uninitialized variables

--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-04-17 22:39 --- Your patch is pre-approved :) -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/31296] Uninitialized variable in _gfortran_unpack0_char

--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-04-17 22:37 --- Index: libgfortran/intrinsics/unpack_generic.c === --- libgfortran/intrinsics/unpack_generic.c (revision 123388) +++ libgfortran/intrinsics/unpac

[Bug fortran/31551] ice in fold_convert, at fold-const.c:2330

--- Comment #9 from dfranke at gcc dot gnu dot org 2007-04-17 22:22 --- > That's right. Daniel, could you confirm that your testcase is indeed > fixed with today's mainline? Confirmed, no more crashes in my code. gcc version 4.3.0 20070417 (experimental) -- ht

[Bug tree-optimization/31606] [4.3 Regression] ICE in try_instantiate_multiple_fields, at tree-sra.c:1601

-- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot |

[Bug rtl-optimization/31360] [4.2 Regression] rtl loop invariant is broken

--- Comment #16 from steven at gcc dot gnu dot org 2007-04-17 22:13 --- Fixeth on ze trunk. -- steven at gcc dot gnu dot org changed: What|Removed |Added Summa

[Bug fortran/31594] gfortran failed to compiled a 'valid' code

--- Comment #6 from steven at gcc dot gnu dot org 2007-04-17 22:09 --- . -- steven at gcc dot gnu dot org changed: What|Removed |Added Status|RESOLVED

[Bug fortran/31551] ice in fold_convert, at fold-const.c:2330

--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-04-17 21:55 --- (In reply to comment #7) > If I follow the thread in this bug list, it seems that this version should > have > the patch applied. That's right. Daniel, could you confirm that your testcase is indeed fixed with t

[Bug c++/31517] [4.1/4.2/4.3 Regression] ICE on invalid initialization of static member of a template class

--- Comment #5 from simartin at gcc dot gnu dot org 2007-04-17 21:50 --- Fixed on all active branches -- simartin at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/31517] [4.1/4.2/4.3 Regression] ICE on invalid initialization of static member of a template class

--- Comment #4 from simartin at gcc dot gnu dot org 2007-04-17 21:46 --- Subject: Bug 31517 Author: simartin Date: Tue Apr 17 21:46:29 2007 New Revision: 123931 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123931 Log: 2007-04-17 Simon Martin <[EMAIL PROTECTED]> PR

[Bug fortran/31551] ice in fold_convert, at fold-const.c:2330

--- Comment #7 from zingale at gmail dot com 2007-04-17 21:32 --- I am seeing internal compiler error: in fold_convert, at fold-const.c:2330 using gcc version 4.3.0 20070417 (experimental) If I follow the thread in this bug list, it seems that this version should have the patch

[Bug target/30483] Internal compiler error with inline volatile assembly on AVR

--- Comment #5 from aesok at gcc dot gnu dot org 2007-04-17 21:23 --- Fixed in 4.1, 4.2 branch, and HEAD. -- aesok at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/30483] Internal compiler error with inline volatile assembly on AVR

--- Comment #4 from aesok at gcc dot gnu dot org 2007-04-17 21:19 --- Subject: Bug 30483 Author: aesok Date: Tue Apr 17 21:19:06 2007 New Revision: 123929 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123929 Log: PR target/30483 * config/avr/avr.c (ptrreg_to_str

[Bug target/30483] Internal compiler error with inline volatile assembly on AVR

--- Comment #3 from aesok at gcc dot gnu dot org 2007-04-17 21:13 --- Subject: Bug 30483 Author: aesok Date: Tue Apr 17 21:13:29 2007 New Revision: 123927 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123927 Log: PR target/30483 * config/avr/avr.c (ptrreg_to_str

[Bug target/30483] Internal compiler error with inline volatile assembly on AVR

--- Comment #2 from aesok at gcc dot gnu dot org 2007-04-17 21:09 --- Subject: Bug 30483 Author: aesok Date: Tue Apr 17 21:08:46 2007 New Revision: 123926 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123926 Log: PR target/30483 * config/avr/avr.c (ptrreg_to_str

[Bug fortran/31609] gfortran segfaults when compiling a module that calls a contained function with an ENTRY point

-- aldot at gcc dot gnu dot org changed: What|Removed |Added CC||aldot at gcc dot gnu dot org Status|UNCONFIRMED

[Bug c++/31517] [4.1/4.2/4.3 Regression] ICE on invalid initialization of static member of a template class

--- Comment #3 from simartin at gcc dot gnu dot org 2007-04-17 20:41 --- Subject: Bug 31517 Author: simartin Date: Tue Apr 17 20:41:12 2007 New Revision: 123925 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123925 Log: 2007-04-17 Simon Martin <[EMAIL PROTECTED]> PR

[Bug tree-optimization/31605] [4.2/4.3 Regression] VRP eliminates a useful test due with conversion from unsigned int to int

--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-17 20:27 --- And it is a bug on the 4.2 branch. Before Ian's patch we got the following ranges for the testcase in comment #2: D.1528_1: VARYING start_2: VARYING D.1528_3: VARYING cur_bitshift_4: ~[0, 0] EQUIVALENCES: { } (0 el

[Bug tree-optimization/31605] [4.3 Regression] VRP eliminates a useful test due with conversion from unsigned int to int

--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-17 20:20 --- This works with "4.2.0 20070309" but that was before the overflow patch to the 4.2 branch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31605

[Bug testsuite/31589] gcc.dg/vect failures due to missing target specifiers

--- Comment #2 from dorit at il dot ibm dot com 2007-04-17 20:10 --- > 2 more are under investigation: > no-section-anchors-vect-69.c > vect-reduc-dot-u16a.c In the first testcase, the vectorizer can only prove that the data reference in the third loop is aligned on 8 bytes. This is eno

[Bug libfortran/31546] add --enable-intermodule

-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Component|fortran |libfortran

[Bug fortran/31612] New: -fsyntax-only documentation is not accurate

The doc for -fsyntax-only says "Check the code for syntax errors, but don’t do anything beyond that." while that option actually does more than that: it creates module files (the *.mod files). If we believe it's an intended behaviour, it should be noted in the docs. If we believe it's not what we

[Bug libfortran/31607] CALL SYSTEM produces garbled output when writing to a buffered file

--- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-17 20:00 --- This is a standard problem even with C code so I don't see why this is specific to fortran or any language. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added -

[Bug middle-end/28071] [4.1 regression] A file that can not be compiled in reasonable time/space

--- Comment #66 from hubicka at ucw dot cz 2007-04-17 19:38 --- Subject: Re: [4.1 regression] A file that can not be compiled in reasonable time/space Just to add some explanation to the numbers, df_scan_ref_pool is 50MB, the bitmaps quoted are 8MB each. Given nature of the testcase,

[Bug tree-optimization/25809] missed PRE optimization - move "invariant casts" out of loops

--- Comment #7 from dorit at il dot ibm dot com 2007-04-17 19:31 --- > so I will look into it. (for reference: http://gcc.gnu.org/ml/gcc-patches/2007-04/msg01103.html). So I guess this should be handled somewhere else. I'll open a new missed-optimization PR instead (not against PRE th

[Bug middle-end/28071] [4.1 regression] A file that can not be compiled in reasonable time/space

--- Comment #65 from hubicka at gcc dot gnu dot org 2007-04-17 19:16 --- I can confirm that at -O2, memory consumption dropped from 0.5GB to 0.28GB, that is indeed good improvement. To summarize http://www.suse.de/~gcctest/memory/results/200704171438/pr28071-O2.rep Compile time wise ma

[Bug fortran/31366] [4.2 only] Last record truncated for read after short write, direct access file

--- Comment #12 from fxcoudert at gcc dot gnu dot org 2007-04-17 19:10 --- This one does not look like a regression. Thomas or Jerry, can you confirm this and close it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31366

[Bug tree-optimization/31611] ICE in remove_referenced_var for loc == *0

--- Comment #2 from aldot at gcc dot gnu dot org 2007-04-17 19:09 --- Created an attachment (id=13382) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13382&action=view) file2 $ gfortran-4.3-HEAD -ffixed-line-length-none -ffree-line-length-none -O1 -ftree-loop-linear -c lattice.f90

[Bug tree-optimization/31522] False overflow warning with phi nodes

--- Comment #11 from ian at airs dot com 2007-04-17 19:08 --- Fixed on mainline. -- ian at airs dot com changed: What|Removed |Added Status|NEW

[Bug fortran/31207] [4.2 only] advance="no" and tabs

--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-04-17 19:08 --- It's not a regression wrt 4.1.2 (just checked) and I don't think it's a regression wrt g77 either, so it's a no. (Plus, with the morbid state of 4.2, I'm not sure we need to put effort there). -- fxcoudert at

[Bug tree-optimization/31611] ICE in remove_referenced_var for loc == *0

--- Comment #1 from aldot at gcc dot gnu dot org 2007-04-17 19:08 --- Created an attachment (id=13381) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13381&action=view) file1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31611

[Bug tree-optimization/31611] New: ICE in remove_referenced_var for loc == *0

trunk, revision 123843 gives for -ftree-loop-linear: Program received signal SIGSEGV, Segmentation fault. 0x082dfc97 in remove_referenced_var (var=0xb7ca961c) at ../../../src/gcc-4.3/gcc/tree-dfa.c:791 791 ggc_free (*loc); (gdb) bt #0 0x082dfc97 in remove_referenced_var (var=0xb7ca961

[Bug c++/31517] [4.1/4.2/4.3 Regression] ICE on invalid initialization of static member of a template class

--- Comment #2 from simartin at gcc dot gnu dot org 2007-04-17 19:06 --- Subject: Bug 31517 Author: simartin Date: Tue Apr 17 19:05:53 2007 New Revision: 123923 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123923 Log: 2007-04-17 Simon Martin <[EMAIL PROTECTED]> PR

[Bug middle-end/30700] [4.2 Regression] YA bogus undefined reference error to static func with -g and -O

--- Comment #8 from hubicka at gcc dot gnu dot org 2007-04-17 19:04 --- Fixed. -- hubicka at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug middle-end/30700] [4.2 Regression] YA bogus undefined reference error to static func with -g and -O

--- Comment #7 from hubicka at gcc dot gnu dot org 2007-04-17 19:02 --- Subject: Bug 30700 Author: hubicka Date: Tue Apr 17 19:02:09 2007 New Revision: 123922 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123922 Log: PR middle-end/30700 * dwarf2out.c (reference_

[Bug preprocessor/14331] please add option to suppress warning message "no newline at end of file"

--- Comment #16 from davek at gcc dot gnu dot org 2007-04-17 18:47 --- Oh, BTW, congratulations Tom on being appointed a libcpp maintainer! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14331

  1   2   >