[Bug c/36692] _Complex __float128 doesn't work

--- Comment #4 from ubizjak at gmail dot com 2008-07-02 06:57 --- (In reply to comment #0) > _Complex __float128 > foo (_Complex __float128 x) > { > return x; > } "typedef _Complex float __attribute__((mode(TC))) _Complex128" will work. BTW: You also can't have "unsigned __int128",

[Bug fortran/36341] MATMUL: Bounds check missing (run time)

--- Comment #13 from tkoenig at gcc dot gnu dot org 2008-07-02 06:54 --- Fixed for compile-time. -- tkoenig at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/36546] Namelist error with tab following a comma and newline

--- Comment #8 from jvdelisle at gcc dot gnu dot org 2008-07-02 05:20 --- Fixed on trunk and 4.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/36657] Namelist reading bug with string constant immediately followed by comment

--- Comment #6 from jvdelisle at gcc dot gnu dot org 2008-07-02 05:18 --- Fixed on Trunk and 4.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/36676] Namelist Comments Problems

--- Comment #8 from jvdelisle at gcc dot gnu dot org 2008-07-02 05:15 --- Fixed on trunk and 4.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/34546] Incorrect array identified in out of bounds runtime error

--- Comment #4 from terry at chem dot gu dot se 2008-07-02 05:11 --- (In reply to comment #3) > I am not sure which patch did this, but I doubt it will be backported to 4.3 It already is in 4.3. ;-) As I said earlier, that warning is produced, but easy to make go away with integer::

[Bug fortran/34546] Incorrect array identified in out of bounds runtime error

--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-07-02 05:06 --- Currently 4.4 is giving: $ gfc bounds.f90 bounds.f90:6.31: write(*,*) JTEJ(0,1000,:) * pT(1000,:) 1 Warning: Array reference at (1) is out of bounds (1000 < 1) in dimension 1

[Bug libfortran/36538] namelist failure with tabs preceding object name

--- Comment #9 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:53 --- Subject: Bug 36538 Author: jvdelisle Date: Wed Jul 2 04:52:47 2008 New Revision: 137337 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137337 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug libfortran/36546] Namelist error with tab following a comma and newline

--- Comment #7 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:53 --- Subject: Bug 36546 Author: jvdelisle Date: Wed Jul 2 04:52:47 2008 New Revision: 137337 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137337 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug fortran/36676] Namelist Comments Problems

--- Comment #7 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:53 --- Subject: Bug 36676 Author: jvdelisle Date: Wed Jul 2 04:52:47 2008 New Revision: 137337 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137337 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug libfortran/36657] Namelist reading bug with string constant immediately followed by comment

--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:53 --- Subject: Bug 36657 Author: jvdelisle Date: Wed Jul 2 04:52:47 2008 New Revision: 137337 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137337 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug libfortran/36657] Namelist reading bug with string constant immediately followed by comment

--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:45 --- Subject: Bug 36657 Author: jvdelisle Date: Wed Jul 2 04:44:21 2008 New Revision: 137336 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137336 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug fortran/36676] Namelist Comments Problems

--- Comment #6 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:45 --- Subject: Bug 36676 Author: jvdelisle Date: Wed Jul 2 04:44:21 2008 New Revision: 137336 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137336 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug libfortran/36546] Namelist error with tab following a comma and newline

--- Comment #6 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:45 --- Subject: Bug 36546 Author: jvdelisle Date: Wed Jul 2 04:44:21 2008 New Revision: 137336 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137336 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED] P

[Bug target/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #6 from masaki dot chikama at gmail dot com 2008-07-02 04:06 --- Thank you. I'll learn more about background of this problem along with your comment. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36686

[Bug fortran/36676] Namelist Comments Problems

--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-07-02 04:02 --- Subject: Bug 36676 Author: jvdelisle Date: Wed Jul 2 04:01:57 2008 New Revision: 137335 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137335 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/36676] Namelist Comments Problems

--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-07-02 03:59 --- Subject: Bug 36676 Author: jvdelisle Date: Wed Jul 2 03:58:57 2008 New Revision: 137334 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137334 Log: 2008-07-01 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug target/36669] Wrong versioning for __float128

--- Comment #21 from hjl dot tools at gmail dot com 2008-07-02 03:52 --- (In reply to comment #19) > This patch > > http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00071.html > > makes all TF symbols with version GCC_4.3.0 while keeping the old > version. > With this patch, on Linux/x8

[Bug target/36684] [4.3/4.4 Regression] spill failure for class 'R0_REGS' on sh4 with -fPIC -O2

--- Comment #5 from kkojima at gcc dot gnu dot org 2008-07-02 03:50 --- SH backend enables insn scheduling before reload for SH4 when the estimated R0 register pressure is low. This PR reveals that it doesn't work well for PIC which will make many implicit R0 uses. It seems that there

[Bug target/36684] [4.3/4.4 Regression] spill failure for class 'R0_REGS' on sh4 with -fPIC -O2

--- Comment #4 from kkojima at gcc dot gnu dot org 2008-07-02 03:47 --- *** Bug 36686 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36684

[Bug target/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #5 from kkojima at gcc dot gnu dot org 2008-07-02 03:47 --- Thanks for the updated testcase. I've confirmed that this PR is a duplicate of PR36684 as you suggested. > Is this a workaround or right fix ? SH backend enables first insn scheduling pass for SH4 when the estimat

[Bug target/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #4 from masaki dot chikama at gmail dot com 2008-07-02 03:20 --- Created an attachment (id=15842) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15842&action=view) preprocessed file without precompiled headers gzipped beacuse plain text file's size is 1.5MB -- htt

[Bug target/36669] Wrong versioning for __float128

--- Comment #20 from hjl dot tools at gmail dot com 2008-07-02 03:17 --- Created an attachment (id=15841) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15841&action=view) A testcase bash-3.2$ gcc --version gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) Copyright (C) 2008 Free Softwar

[Bug target/36669] Wrong versioning for __float128

--- Comment #19 from hjl dot tools at gmail dot com 2008-07-02 03:15 --- This patch http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00071.html makes all TF symbols with version GCC_4.3.0 while keeping the old version. -- hjl dot tools at gmail dot com changed: What|Re

[Bug target/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #3 from masaki dot chikama at gmail dot com 2008-07-02 03:14 --- >Could you please send the testcase without using precompiled headers? Do you mean that I should redo without "-include .pch/release-shared/QtGui" ? I'll attach in next post. >Does -fno-schedule-insns get rid

[Bug fortran/34546] Incorrect array identified in out of bounds runtime error

--- Comment #2 from terry at chem dot gu dot se 2008-07-02 02:10 --- A gentle reminder: This problem still exists as of 4.3.2 20080626. (At least a compile-time warning is generated for Daniel's testcase. If that 1000 index is an integer variable, however, the compile-time warning goe

[Bug c/36692] _Complex __float128 doesn't work

--- Comment #3 from pinskia at gcc dot gnu dot org 2008-07-02 02:04 --- Not internally in GCC :). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36692

[Bug c/36692] _Complex __float128 doesn't work

--- Comment #2 from hjl dot tools at gmail dot com 2008-07-02 01:25 --- __float128 is a fundamental scalar type in x86-64 psABI, similar to float. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36692

[Bug bootstrap/36481] gcc fails to build on Solaris x86 - it forgets the locations of libmpfr

--- Comment #3 from BlanchardJ at ieee dot org 2008-07-02 00:59 --- (In reply to comment #2) > Subject: Re: gcc fails to build on Solaris x86 - it > forgets the locations of libmpfr > > pinskia at gcc dot gnu dot org wrote: > > --- Comment #1 from pinskia at gcc dot gnu dot org 2

[Bug c/36692] _Complex __float128 doesn't work

--- Comment #1 from pinskia at gcc dot gnu dot org 2008-07-02 00:44 --- __float128 is a typedef. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36692

[Bug c/36692] New: _Complex __float128 doesn't work

[EMAIL PROTECTED] floa128-3]$ cat x.c __float128 bar (__float128 x) { return x; } _Complex __float128 foo (_Complex __float128 x) { return x; } [EMAIL PROTECTED] floa128-3]$ make x.s /export/build/gnu/gcc-float128/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/gcc-float128/build-x86_64-linux

[Bug target/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #2 from kkojima at gcc dot gnu dot org 2008-07-02 00:20 --- Could you please send the testcase without using precompiled headers? See http://gcc.gnu.org/bugs.html#pch. I also suspect this is a duplicate of PR36684. Does -fno-schedule-insns get rid of this error? -- kkoj

[Bug target/36684] [4.3/4.4 Regression] spill failure for class 'R0_REGS' on sh4 with -fPIC -O2

--- Comment #3 from kkojima at gcc dot gnu dot org 2008-07-01 23:59 --- A reduced testcase: typedef int (proc) (int *interp, void *data); typedef struct { void *func; void *data; } InterStruct; extern InterStruct simple; extern int simple_interactor (); static proc *interactor = si

[Bug fortran/36689] PRINT and WRITE eat minus sign

--- Comment #3 from dennis dot wassel at googlemail dot com 2008-07-01 22:55 --- (In reply to comment #1) > Not that it helps much, but on x86-64-linux I cannot reproduce this using GCC > 4.1, 4.2, 4.3.1 and 4.4.0(of today). Though I agree that the bug is > irritating. Same with me, wo

[Bug c/36691] New: wrong value left in induction variable

[EMAIL PROTECTED] tmp35]$ current-gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../configure --program-prefix=current- --enable-languages=c,c++ --prefix=/home/regehr Thread model: posix gcc version 4.4.0 20080701 (experimental) (GCC) [EMAIL PROTECTED] tmp35]$ cat small.c

[Bug target/36622] 4.3.1 failed to compile gcse.c file.

--- Comment #18 from imam dot toufique at intel dot com 2008-07-01 21:17 --- (In reply to comment #17) > (In reply to comment #16) > > (In reply to comment #15) > > > I did: > > > > > > >svn co http://gcc.gnu.org/svn/gcc/branches/gcc-4_3-branch/ gcc-4.3 > > > > > > I hope I got the

[Bug fortran/36689] PRINT and WRITE eat minus sign

--- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-07-01 19:32 --- Do you see the problem if XP is not declared a pointer? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36689

[Bug target/36622] 4.3.1 failed to compile gcse.c file.

--- Comment #17 from imam dot toufique at intel dot com 2008-07-01 19:26 --- (In reply to comment #16) > (In reply to comment #15) > > I did: > > > > >svn co http://gcc.gnu.org/svn/gcc/branches/gcc-4_3-branch/ gcc-4.3 > > > > I hope I got the correct copy there, unless I did some wr

[Bug fortran/36683] -fbounds-check failure for allocated array and spread

-- tkoenig at gcc dot gnu dot org changed: What|Removed |Added OtherBugsDependingO||34670 nThis|| S

[Bug target/36613] [4.1/4.2/4.3/4.4 Regression] likely codegen bug

--- Comment #7 from matz at gcc dot gnu dot org 2008-07-01 19:17 --- Blaeh. The bug is in code that is there since the dawn of revision control, under a comment that starts with "... This is tricky ..." and ends with "I am not sure whether the algorithm here is always right ...". One t

[Bug fortran/36670] Missing compile-time checks on sum and product

-- tkoenig at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |tkoenig at gcc dot gnu dot |dot org

[Bug fortran/35423] Implement OpenMP workshare

--- Comment #2 from burnus at gcc dot gnu dot org 2008-07-01 18:08 --- First patch: http://gcc.gnu.org/ml/fortran/2008-06/msg00281.html -- burnus at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/36689] PRINT and WRITE eat minus sign

--- Comment #1 from burnus at gcc dot gnu dot org 2008-07-01 18:06 --- Not that it helps much, but on x86-64-linux I cannot reproduce this using GCC 4.1, 4.2, 4.3.1 and 4.4.0(of today). Though I agree that the bug is irritating. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36689

[Bug other/31754] Include column number along line in error messages main.cpp:5:38

--- Comment #14 from dseketel at redhat dot com 2008-07-01 16:29 --- Hello, Just a quick comment on this bug. I think that in the example you gave, gcc (at the least 4.3.0 version) is giving a correct column location. The expression gcc is complaining about is: "a +- b". That expres

Re: Template type bug

Sorry for the incomplete previous mail, which was spuriously sent... Hello again, a little addition to my previous post: In a non-main c++ file (say A.cpp), I write the code template int max (int x, int y); // OK template double max (double x, double y); // Fails in order to instan

Re: Template type bug

Hello again, a little addition to my previous post: In a non-main c++ file (say A.cpp), I write the code template int max (int x, int y); // OK template double max (double x, double y); // Fails in order to instantiate the template, so that the function "double max(double,double)"

[Bug debug/36690] [4.3/4.4 Regression] .debug_line first line is behind the first instruction

--- Comment #1 from jsm28 at gcc dot gnu dot org 2008-07-01 15:52 --- I've also observed this problem (as causing a number of GDB testsuite failures). With both 4.2 and 4.3, the function prologue is followed by a jump, the loop body, and then the test of the loop condition which the jum

[Bug tree-optimization/36387] [4.2/4.3 Regression] points-to variables not transitively clobbered

--- Comment #5 from rguenth at gcc dot gnu dot org 2008-07-01 15:35 --- This is fixed on the trunk. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Kn

[Bug debug/36690] New: .debug_line first line is behind the first instruction

rsion-Release number of selected component (if applicable): gcc-4.3.1-3.x86_64 (Fedora 9, broken) Fedora 8 was correct: gcc-4.1.2-33.x86_64 Verified as broken on: GNU C (GCC) version 4.4.0 20080701 (experimental) (x86_64-unknown-linux-gnu) compiled by GNU C version 3.4.6 20060404 (Red Hat 3.

[Bug fortran/36689] New: PRINT and WRITE eat minus sign

Funny things abound... Negative numbers show up as positive, which can be pretty -let's say- irritating in computational applications :) I've managed to boil this down to the following example PROGRAM Minus implicit none integer :: N real, pointer, dimension(:) :: XP => NULL() N = 2 a

[Bug middle-end/34744] Memory leaks in compiler with empty program

--- Comment #4 from zadeck at gcc dot gnu dot org 2008-07-01 14:06 --- Subject: Bug 34744 Author: zadeck Date: Tue Jul 1 14:05:13 2008 New Revision: 137319 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137319 Log: 2008-07-01 Kenneth Zadeck <[EMAIL PROTECTED]> PR rtl-

[Bug c/36688] New: Incorrect struct assignments with nested const initializers

g++ 4.3 and higher produces incorrect struct assignments with nested constant initializers. In the example, the assignment x = init_x initializes the struct with zero's, not with {{1,2,3},0}. gcc versions: gcc 4.3.2 (svn, 2008/07/01, rev. 137317) gcc 4.4.0 (svn, 2008/06/24) gcc 3.3.3 and gc

[Bug middle-end/34744] Memory leaks in compiler with empty program

--- Comment #3 from zadeck at gcc dot gnu dot org 2008-07-01 13:57 --- Subject: Bug 34744 Author: zadeck Date: Tue Jul 1 13:56:28 2008 New Revision: 137318 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137318 Log: Marked changelog entry with PR rtl-optimization/34744 Modified

[Bug middle-end/34744] Memory leaks in compiler with empty program

--- Comment #2 from zadeck at naturalbridge dot com 2008-07-01 13:53 --- Fixed as revision 137284 and 137285. -- zadeck at naturalbridge dot com changed: What|Removed |Added -

[Bug c++/36687] g++ can not compile dbcheck.cpp of MythTV

--- Comment #1 from danielk at cuymedia dot net 2008-07-01 13:31 --- Created an attachment (id=15840) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15840&action=view) Preprocessor output for failing file Note: I should also note memory consumption by gcc is very high when compilin

[Bug c++/36687] New: g++ can not compile dbcheck.cpp of MythTV

Note this is the case with both the 0.21-fixes and trunk of mythtv, same file. * the exact version of GCC; gcc (Ubuntu 4.3.1-3ubuntu1) 4.3.1 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHA

[Bug middle-end/36684] [4.3 Regression] compile failure with message "unable to find a register to spill in class 'R0_REGS'"

-- jakub at gcc dot gnu dot org changed: What|Removed |Added Priority|P3 |P4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36684

[Bug c++/36685] clarify/diagnose use of weak constant

--- Comment #2 from joseph at codesourcery dot com 2008-07-01 11:35 --- Subject: Re: New: clarify/diagnose use of weak constant See the inconclusive discussion at (the original message was the previous month), and bug 3

[Bug tree-optimization/36666] [4.4 Regression] ICE in process_constraint, at tree-ssa-structalias.c:2573

--- Comment #5 from rguenth at gcc dot gnu dot org 2008-07-01 11:06 --- Subject: Bug 3 Author: rguenth Date: Tue Jul 1 11:05:17 2008 New Revision: 137315 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137315 Log: 2008-07-01 Richard Guenther <[EMAIL PROTECTED]> PR

[Bug tree-optimization/36666] [4.4 Regression] ICE in process_constraint, at tree-ssa-structalias.c:2573

--- Comment #4 from rguenth at gcc dot gnu dot org 2008-07-01 11:05 --- Fixed. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug c++/36685] clarify/diagnose use of weak constant

--- Comment #1 from algrant at acm dot org 2008-07-01 10:21 --- Similar argument applies to __attribute__((visibility("default"))) . -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36685

[Bug c++/36686] [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #1 from masaki dot chikama at gmail dot com 2008-07-01 10:13 --- Created an attachment (id=15839) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15839&action=view) preprocessed file generated by adding -save-temps -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3668

[Bug c++/36686] New: [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'"

gcc-4.3.0 fails to compile with this message when compiling qt-4.3.4. gcc-4.1.3 can compile without fail. They are both natively running on sh4 board. The message is very similar with Bug #36684. They may have the same root cause. g++ -c -include .pch/release-shared/QtGui -pipe -fno-exceptions

[Bug c++/36685] New: clarify/diagnose use of weak constant

Consider this: __attribute__((weak)) extern int const K = 7; int f(void) { return K; } int a[K]; Assuming the combination of 'weak' and 'const' is legitimate (and it seems useful enough to allow), the compiler should avoid the constant-promotion optimization when generating f(), and should

[Bug middle-end/36684] [4.3 Regression] compile failure with message "unable to find a register to spill in class 'R0_REGS'"

-- rguenth at gcc dot gnu dot org changed: What|Removed |Added Component|c |middle-end Summary|[4.3 regression] compile|[4.3 Regre

[Bug c/36684] [4.3 regression] compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #2 from masaki dot chikama at gmail dot com 2008-07-01 09:41 --- Sorry. "/tmp/ccjGJhgH.out" is another try's message. Attached file(ccOOu6ip.out) are produced with same message. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36684

[Bug c/36684] [4.3 regression] compile failure with message "unable to find a register to spill in class 'R0_REGS'"

--- Comment #1 from masaki dot chikama at gmail dot com 2008-07-01 09:34 --- Created an attachment (id=15838) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15838&action=view) ccOOu6ip.out -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36684

[Bug c/36684] New: [4.3 regression] compile failure with message "unable to find a register to spill in class 'R0_REGS'"

gcc-4.3.0 fails to compile with this message when compiling expect-5.43.0. gcc-4.1.3 can compile without fail. They are both natively running on sh4 board. gcc -c -I. -I. -I/usr/include/tcl-private/generic -DEXP_VERSION=\"5.43.0\" -DSCRIPTDIR=\"/usr/share/tcl8.5/expect5.43\" -DEXEC

[Bug target/36669] Wrong versioning for __float128

--- Comment #18 from rguenth at gcc dot gnu dot org 2008-07-01 08:56 --- We cannot "fix" this after the fact. And it's IMHO not worth it either. We could add the symbol to GCC_4.3.0 as well and make that the default though. -- rguenth at gcc dot gnu dot org changed: Wha

[Bug fortran/36681] compiler error message with gfortran 4.3.1 but not with 4.2.1

--- Comment #2 from dfranke at gcc dot gnu dot org 2008-07-01 08:22 --- Very similar to, if not a dupe of, PR36590. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36681