[Bug fortran/32903] [regression] Default initializer and intent(OUT): default initializer not used
--- Comment #4 from pault at gcc dot gnu dot org 2007-07-27 09:04 --- Fixed as obvious. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32903
[Bug fortran/32035] '' may be used uninitialized in this function
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2007-07-27 14:28 --- Fixed on mainline. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32035
[Bug fortran/32035] '' may be used uninitialized in this function
--- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-07-27 14:26 --- Subject: Bug 32035 Author: fxcoudert Date: Fri Jul 27 14:26:43 2007 New Revision: 126978 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126978 Log: PR fortran/32035 * trans-stmt.c (gfc_trans_character_select): Replace the mechanism with labels by a SWITCH_EXPR. * trans-decl.c (gfc_build_builtin_function_decls): Change return type for select_string. * runtime/select.c (select_string): Adjust prototype and function so that the return value is an integer, not a pointer. * gfortran.dg/select_char_1.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/select_char_1.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c trunk/gcc/fortran/trans-stmt.c trunk/gcc/testsuite/ChangeLog trunk/libgfortran/ChangeLog trunk/libgfortran/runtime/select.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32035
[Bug tree-optimization/32845] [4.3 Regression] : gcc.dg/builtins-61.c scan-tree-dump return 0.0
--- Comment #1 from danglin at gcc dot gnu dot org 2007-07-27 14:46 --- Also occurs on hppa-linux. -- danglin at gcc dot gnu dot org changed: What|Removed |Added CC||danglin at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32845
[Bug debug/32914] New: ICE with -g option
Testcase
"test-ice.cpp"
#include
#include
const __m128i tmp={0,0};
g++ -O3 -g -c -msse2 test-ice.cpp
I get the following error:
test-ice.cpp:5: internal compiler error: in rtl_for_decl_init, at
dwarf2out.c:10071
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
It compiles fine with "-g" option. This issue is there even in 4.3 mainline as
well.
I tracked this problem to this patch
(http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01567.html).
Using the following temporary patch fixes this issue. I was basically reverting
the line which causes this issue.
--- dwarf2out.c.orig2007-07-25 10:29:24.790178000 -0500
+++ dwarf2out.c 2007-07-25 10:21:41.378252000 -0500
@@ -10065,8 +10065,8 @@ rtl_for_decl_init (tree init, tree type)
immediate RTL constant, expand it now. We must be careful not to
reference variables which won't be output. */
- else if (initializer_constant_valid_p (init, type)
- && ! walk_tree (&init, reference_to_unused,NULL,NULL)
+else if ((INTEGRAL_TYPE_P (type) || SCALAR_FLOAT_TYPE_P (type))
+&& initializer_constant_valid_p (init, type))
{
rtl = expand_expr (init, NULL_RTX, VOIDmode, EXPAND_INITIALIZER);
Thanks,
- Dwarak
--
Summary: ICE with -g option
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dwarak dot rajagopal at amd dot com
GCC build triplet: x86_64
GCC host triplet: x86_64
GCC target triplet: x86_64
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32914
[Bug target/11180] [avr-gcc] Optimization decrease performance of struct assignment.
--- Comment #11 from eweddington at cso dot atmel dot com 2007-07-27 14:23 --- Subject: RE: [avr-gcc] Optimization decrease performance of struct assignment. > --- Comment #10 from dmixm at marine dot febras dot ru > 2007-07-27 01:24 --- > Yes, results are: > > avr-gcc-3.3.6: O0 --> 75, O1,O2,O3,Os --> 79 > avr-gcc-4.2.1: O0 --> 109, O1,O2,O3,Os --> 79 > > The mistake is corrected? It is possible to tell and so as now > application of keys of optimization shortens a code. However, > "correction" does not improve quality of optimization, it only worsens > not optimized code. Agreed. But is this sufficient to close this bug report? Eric -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11180
[Bug testsuite/32471] Testcases which always fail on targets where an int is 16 bits
--- Comment #1 from patchapp at dberlin dot org 2007-07-27 16:00 --- Subject: Bug number PR testsuite/32471 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01988.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32471
[Bug target/32915] New: ICE while compiling libgfortran/io/write.c
Bootstrap including gfortran has been broken on native i386-pc-mingw32 for at
least 10 days, with the C compiler having an ICE while compiling
libgfortran/io/write.c. I finally found the opportunity to reduce the ICE to
the following code:
$ cat write.i
extern void fflush (int);
extern __attribute__ ((__dllimport__)) int _iob[];
static int __gthrw_pthread_once () __attribute__
((__weakref__("pthread_once")));
void flush_if_preconnected ()
{
fflush (_iob[0]);
}
$ C:/msys/1.0.10/home/FX/ibin/gcc/cc1.exe write.i -quiet
write.i:8: internal compiler error: Segmentation fault
The backtrace I could get from gdb looks seriously garbled:
Program received signal SIGSEGV, Segmentation fault.
decl_assembler_name_equal (decl=0x2ae2360, asmname=0x2ae1930)
at ../../trunk/gcc/tree.c:323
323 if (IDENTIFIER_POINTER (decl_asmname)[0] == '*')
(gdb) where
#0 decl_assembler_name_equal (decl=0x2ae2360, asmname=0x2ae1930)
at ../../trunk/gcc/tree.c:323
#1 0x00512973 in decl_assembler_name_equal (decl=0x2ae1930,
asmname=0x290f200) at ../../trunk/gcc/tree.c:314
#2 0x00512973 in decl_assembler_name_equal (decl=0x0, asmname=0x3d2412)
at ../../trunk/gcc/tree.c:314
#3 0x00512973 in decl_assembler_name_equal (decl=0x3d2412, asmname=0x0)
at ../../trunk/gcc/tree.c:314
#4 0x00512973 in decl_assembler_name_equal (decl=0x3d2412, asmname=0x0)
at ../../trunk/gcc/tree.c:314
#5 0x00512973 in decl_assembler_name_equal (decl=0x0, asmname=0x0)
at ../../trunk/gcc/tree.c:314
#6 0x00512973 in decl_assembler_name_equal (decl=0x3, asmname=0x3d24a0)
at ../../trunk/gcc/tree.c:314
#7 0x00512973 in decl_assembler_name_equal (decl=0x3a, asmname=0x4)
at ../../trunk/gcc/tree.c:314
#8 0x00512973 in decl_assembler_name_equal (decl=0x1, asmname=0x9)
at ../../trunk/gcc/tree.c:314
#9 0x00512973 in decl_assembler_name_equal (decl=0x0, asmname=0x2)
at ../../trunk/gcc/tree.c:314
#10 0x00512973 in decl_assembler_name_equal (decl=0x401280, asmname=0x0)
at ../../trunk/gcc/tree.c:314
#11 0x00512973 in decl_assembler_name_equal (decl=)
at ../../trunk/gcc/tree.c:314
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--
Summary: ICE while compiling libgfortran/io/write.c
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: fxcoudert at gcc dot gnu dot org
GCC build triplet: i386-pc-mingw32
GCC host triplet: i386-pc-mingw32
GCC target triplet: i386-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32915
[Bug fortran/32760] Error defining subroutine named PRINT
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2007-07-27 16:30 --- Subject: Bug 32760 Author: jvdelisle Date: Fri Jul 27 16:30:10 2007 New Revision: 126981 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126981 Log: 2007-07-27 Jerry DeLisle <[EMAIL PROTECTED]> Daniel Franke <[EMAIL PROTECTED]> PR fortran/32760 * primary.c (match_variable): Do not call gfc_add_flavor if symbol has attribute of ACCESS_PUBLIC or ACCESS_PRIVATE already marked. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/primary.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32760
[Bug libfortran/23272] [mingw32] inquire via filename fails
--- Comment #7 from fxcoudert at gcc dot gnu dot org 2007-07-27 11:24 --- (In reply to comment #6) > should one add a mingw maintainer to the CC? Adding Danny Smith to the CC list. > BTW, this one misses the wrong-code keyword (and I don't have permission to > add > it, which is annoying). Added. I can't give you permission to add keywords, the only thing I can do is make you a CONFIRMer (which I just did). -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added CC||dannysmith at gcc dot gnu ||dot org Keywords||wrong-code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23272
[Bug c++/32912] New: [Regression] ICE with C99 compound literal expression
Compiling the test case below gives the following ICE:
> bug.C: In function 'void bar()':
> bug.C:30: internal compiler error: in build_int_cst_wide, at tree.c:890
> Please submit a full bug report,
I think this might be related to bug 20103, except that gcc-4.1 handles the
test case just fine. The test case also compiles in 4.3 with -O{0,1,s} instead
of -O{2,3}. -ftree-pre is the culprit flag -- removing it from -O2 or adding it
to -O1 toggles the bug.
// g++-4.3-20070716 -msse3 -O2 bug.C
#include
// Must be a vector, not a scalar
#if 0
typedef long v2d;
#else
typedef __m128i v2d;
#endif
v2d rval();
v2d g;
struct A { // Must have 2+ members
v2d a;
v2d b;
};
struct B { // Need a struct containing an A
A a;
};
struct C {
operator A() {
v2d l;
A a;
// Must compute (a ^ ~b). Neither (a ^ b) nor (a + ~b) breaks.
a.a ^= ~a.b; // globals, locals, and rvals don't break
a.a ^= ~(v2d) {0,0}; // members and compound literals do
return a;
}
};
void foo(B);
void bar() {
foo((B){C()});
}
--
Summary: [Regression] ICE with C99 compound literal expression
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: scovich at gmail dot com
GCC target triplet: x86_64-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32912
[Bug fortran/32903] [regression] Default initializer and intent(OUT): default initializer not used
--- Comment #3 from pault at gcc dot gnu dot org 2007-07-27 09:03 --- Subject: Bug 32903 Author: pault Date: Fri Jul 27 09:03:41 2007 New Revision: 126974 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126974 Log: 2007-07-27 Paul Thomas <[EMAIL PROTECTED]> PR fortran/32903 * trans-decl.c (gfc_trans_deferred_vars): Set intent(out) derived types as referenced, if they have the the default initializer set. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32903
[Bug middle-end/32911] Function __attribute__ ((idempotent))
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-27 09:35 --- The Java front-end has the same problem. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Component|c |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
[Bug rtl-optimization/32475] [4.3 Regression] function with asm() does not setup stack frame
--- Comment #25 from pinskia at gcc dot gnu dot org 2007-07-27 09:42 --- Fixed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32475
[Bug fortran/32903] [regression] Default initializer and intent(OUT): default initializer not used
--- Comment #5 from burnus at gcc dot gnu dot org 2007-07-27 09:50 --- Subject: Bug 32903 Author: burnus Date: Fri Jul 27 09:49:55 2007 New Revision: 126975 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126975 Log: 2007-07-27 Tobias Burnus <[EMAIL PROTECTED]> PR fortran/32903 * gfortran.dg/initialization_11.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/initialization_11.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32903
[Bug libstdc++/32910] The == operator of hashtable.h and hash_map.h is broken
--- Comment #1 from pcarlini at suse dot de 2007-07-27 09:26 --- Note that we are talking about one of the *legacy*, extension, HP/SGI containers: those in general are only minimally maintained these days because standard replacements are being prepared for C++0x and already available in TR1: basically, we care only about serious regressions. That particular behavior, evidently on purpose in the implementation (i.e., the initial comparison of the number of buckets) has remained like this for some 12 years and will not be changed now, sorry. Well, also note that it's debatable whether and which equality operator makes sense for an unordered container, the ones currently standardized for example miss comparison operators completely. -- pcarlini at suse dot de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32910
[Bug fortran/31211] wrong code generated for pointer returning function as actual argument
--- Comment #8 from patchapp at dberlin dot org 2007-07-27 10:55 --- Subject: Bug number PR31211 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01975.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31211
[Bug fortran/32682] [4.3 Regression] ICE in gfc_trans_array_constructor, at fortran/trans-array.c:1664
--- Comment #6 from pault at gcc dot gnu dot org 2007-07-27 15:09 --- (In reply to comment #5) > Paul, any plans to get the fix from comment #3 into trunk? > Gee, Daniel - I had totally forgotten this one. Will do. Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32682
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #11 from fxcoudert at gcc dot gnu dot org 2007-07-27 14:47
---
Here is the shortest Fortran testcase I could come with:
$ cat a.f90
subroutine foo
integer :: i
do
i = i + 1
select case (' ')
case default
call bar (i + 1, i - 1)
end select
enddo
end subroutine foo
$ gfortran -O2 -c a.f90
Unable to coalesce ssa_names 1 and 3 which are marked as MUST COALESCE.
i_1(ab) and i_3(ab)
a.f90: In function foo:
a.f90:1: internal compiler error: SSA corruption
I tried to make a C testcase from the original tree dump of this Fortran code,
but couldn't reproduce the ICE. It probably depends on the exact blocks
inserted.
Anyway, please note that starting with rev. 126978, the Fortran front-end emits
different code for this code (due to better translation of SELECT for character
variables, fixing PR32035), and thus the ICE is not triggered by the reporter's
code (nor is it triggered by my reduced testcase).
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu dot
||org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|-00-00 00:00:00 |2007-07-27 14:47:48
date||
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug libfortran/23272] [mingw32] inquire via filename fails
--- Comment #8 from jv244 at cam dot ac dot uk 2007-07-27 12:03 --- (In reply to comment #7) > Added. I can't give you permission to add keywords, the only thing I can do is > make you a CONFIRMer (which I just did). OK, I might use that from time to time. Who has the power to allow me to add/change keywords? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23272
[Bug middle-end/32913] New: -fprofile-generate/use: Program 24% slower than without
This is with the polyhedron test "fatigue" on AMD Athlon64 X2 4800+ with openSUSE 10.3b6 x86-64 and today's GCC 4.3.0 20070727. Test case available from: http://www.polyhedron.co.uk/MFL6VW74649 Using on one hand gfortran -march=opteron -ffast-math -funroll-loops -ftree-loop-linear -ftree-vectorize -msse3 -O3 fatigue.f90 and on the other hand the same with once -fprofile-generate and then, after one ./a.out run, -fprofile-use. http://physik.fu-berlin.de/~tburnus/gcc-trunk/benchmark/#rt Result: 12.32s [100] 15.30s [124] thus the profile-use case is 24% slower. This seems to be no regression as the non-profile version became faster around 2007-03-20 whereas the profile-use version stayed at the old execution time. -- Summary: -fprofile-generate/use: Program 24% slower than without Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32913
[Bug target/32853] [4.3 regression] failing libjava testcases
--- Comment #2 from debian-gcc at lists dot debian dot org 2007-07-27 16:57 --- this is not a bug in gij, but in glibc (2.6?), apparently fixed by: 2006-11-30 Jan Kratochvil <[EMAIL PROTECTED]> * sysdeps/unix/sysv/linux/x86_64/clone.S: Provide CFI for the outermost `clone' function to ensure proper unwinding stop of gdb. and 2006-11-30 Jan Kratochvil <[EMAIL PROTECTED]> * sysdeps/unix/sysv/linux/i386/clone.S: Provide CFI for the outermost `clone' function to ensure proper unwinding stop of gdb. found in the glibc FC branch, but not in HEAD and glibc-2_6-branch. Matthias -- debian-gcc at lists dot debian dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32853
[Bug fortran/32760] Error defining subroutine named PRINT
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2007-07-27 16:34 --- Subject: Bug 32760 Author: jvdelisle Date: Fri Jul 27 16:33:50 2007 New Revision: 126982 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126982 Log: 2007-07-27 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/32760 * gfortran.dg/private_type_7.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/private_type_7.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32760
[Bug libstdc++/32916] file stream error writing large buffers
--- Comment #2 from pcarlini at suse dot de 2007-07-27 17:14 --- ... actually, if you are on a 32-bit machine, your code is invalid, because ostream::write takes a streamsize as second argument, which is a ptrdiff_t. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug libstdc++/32907] Inefficient operator== in std::string
--- Comment #3 from paolo at gcc dot gnu dot org 2007-07-27 17:25 --- Subject: Bug 32907 Author: paolo Date: Fri Jul 27 17:25:04 2007 New Revision: 126988 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126988 Log: 2007-07-27 Paolo Carlini <[EMAIL PROTECTED]> PR libstdc++/32907 * include/bits/basic_string.h (operator==(const basic_string<_CharT>&, const basic_string<_CharT>&)): Add. (operator!=): Forward to operator==. * include/ext/vstring.h(operator==(const __versa_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT>, _Base>&, const __versa_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT>, _Base>&)): Add. (operator!=): Forward to operator==. * include/ext/sso_string_base.h (_M_compare): Remove. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/basic_string.h trunk/libstdc++-v3/include/ext/sso_string_base.h trunk/libstdc++-v3/include/ext/vstring.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32907
[Bug libstdc++/32907] Inefficient operator== in std::string
--- Comment #4 from pcarlini at suse dot de 2007-07-27 17:25 --- Fixed for 4.3.0. -- pcarlini at suse dot de changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32907
[Bug fortran/32899] [4.3 regresssion] Broken diagnostic for invalid use of .eq. for logicals
--- Comment #4 from kargl at gcc dot gnu dot org 2007-07-27 17:00 --- Fixed on trunk. -- kargl at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32899
[Bug libstdc++/32916] New: file stream error writing large buffers
g++ (or libstdc++ to be more exact) failed on the following simple testcase:
#include
#include
#include
int main()
{
try {
const size_t bufsize = 2252778560;
char* buf = new char[bufsize];
std::memset(buf, 0x22, bufsize);
std::ofstream o("test.data");
o.write(buf, bufsize);
if (o.fail()) {
std::cerr << " write failed, rdstate: " << o.rdstate() << std::endl;
if (o.bad()) {
std::cerr << "bad\n";
}
}
}
catch (...) {
std::cerr << "exception!\n";
}
}
output of the program :
./a.out
write failed, rdstate: 1 bad
when it was compiled with g++ 4.1.2
with g++ 3.2.3 the test works fine
sample compiler invocation:
/gcc/v4.1.2p1/bin/g++ -m64 test_write.cpp
--
Summary: file stream error writing large buffers
Product: gcc
Version: 4.1.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: satyaakam at yahoo dot co dot in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug middle-end/32749] [4.3 regression]: gfortran.dg/auto_array_1.f90
--- Comment #25 from zadeck at naturalbridge dot com 2007-07-27 17:29
---
Subject: Re: [4.3 regression]: gfortran.dg/auto_array_1.f90
This patch rearranges the updating of the local dataflow info when
building reg_dead notes. The need for this was that processing was not
correctly handled for clobbers that occurred within conditional call
insns. A rare case but one that at least happens on the ia-64.
This patch not only fixes the regressions listed in pr32749, but also
fixes the gfortran.dg/matmul_3.f90 on the ia-64 regressions.
This patch was bootstrapped and regression tested yesterday on x86-64
and ia-64 and was again bootstrapped this morning on x86-64 (just to
make sure there were no interactions with richard sandiford's fixes to
closely related code that was just committed.)
Committed as revision 126987.
Kenny
2007-07-26 Kenneth Zadeck <[EMAIL PROTECTED]>
PR middle-end/32749
* df-problems.c (df_create_unused_note): Removed do_not_gen parm
and the updating of the live and do_not_gen sets.
(df_note_bb_compute): Added updating of live and do_not_gen sets
for regular defs so that the case of clobber inside conditional
call is processed correctly.
Index: df-problems.c
===
--- df-problems.c (revision 126979)
+++ df-problems.c (working copy)
@@ -3868,13 +3868,12 @@ df_set_dead_notes_for_mw (rtx insn, rtx
}
-/* Create a REG_UNUSED note if necessary for DEF in INSN updating LIVE
- and DO_NOT_GEN. Do not generate notes for registers in artificial
- uses. */
+/* Create a REG_UNUSED note if necessary for DEF in INSN updating
+ LIVE. Do not generate notes for registers in ARTIFICIAL_USES. */
static rtx
df_create_unused_note (rtx insn, rtx old, struct df_ref *def,
- bitmap live, bitmap do_not_gen, bitmap artificial_uses)
+ bitmap live, bitmap artificial_uses)
{
unsigned int dregno = DF_REF_REGNO (def);
@@ -3899,12 +3898,6 @@ df_create_unused_note (rtx insn, rtx old
#endif
}
- if (!(DF_REF_FLAGS (def) & (DF_REF_MUST_CLOBBER + DF_REF_MAY_CLOBBER)))
-bitmap_set_bit (do_not_gen, dregno);
-
- /* Kill this register if it is not a subreg store or conditional store. */
- if (!(DF_REF_FLAGS (def) & (DF_REF_PARTIAL | DF_REF_CONDITIONAL)))
-bitmap_clear_bit (live, dregno);
return old;
}
@@ -3915,7 +3908,7 @@ df_create_unused_note (rtx insn, rtx old
static void
df_note_bb_compute (unsigned int bb_index,
- bitmap live, bitmap do_not_gen, bitmap artificial_uses)
+ bitmap live, bitmap do_not_gen, bitmap artificial_uses)
{
basic_block bb = BASIC_BLOCK (bb_index);
rtx insn;
@@ -4012,17 +4005,17 @@ df_note_bb_compute (unsigned int bb_inde
for (def_rec = DF_INSN_UID_DEFS (uid); *def_rec; def_rec++)
{
struct df_ref *def = *def_rec;
- if (!(DF_REF_FLAGS (def) & (DF_REF_MUST_CLOBBER |
DF_REF_MAY_CLOBBER)))
- old_unused_notes
- = df_create_unused_note (insn, old_unused_notes,
- def, live, do_not_gen,
- artificial_uses);
-
- /* However a may or must clobber still needs to kill the
-reg so that REG_DEAD notes are later placed
-appropriately. */
- else
- bitmap_clear_bit (live, DF_REF_REGNO (def));
+ unsigned int dregno = DF_REF_REGNO (def);
+ if (!DF_REF_FLAGS_IS_SET (def, DF_REF_MUST_CLOBBER |
DF_REF_MAY_CLOBBER))
+ {
+ old_unused_notes
+ = df_create_unused_note (insn, old_unused_notes,
+def, live, artificial_uses);
+ bitmap_set_bit (do_not_gen, dregno);
+ }
+
+ if (!DF_REF_FLAGS_IS_SET (def, DF_REF_PARTIAL |
DF_REF_CONDITIONAL))
+ bitmap_clear_bit (live, dregno);
}
}
else
@@ -4043,10 +4036,16 @@ df_note_bb_compute (unsigned int bb_inde
for (def_rec = DF_INSN_UID_DEFS (uid); *def_rec; def_rec++)
{
struct df_ref *def = *def_rec;
+ unsigned int dregno = DF_REF_REGNO (def);
old_unused_notes
= df_create_unused_note (insn, old_unused_notes,
-def, live, do_not_gen,
-artificial_uses);
+def, live, artificial_uses);
+
+ if (!DF_REF_FLAGS_IS_SET (def, DF_REF_MUST_CLOBBER |
DF_REF_MAY_CLOBBER))
+ bitmap_set_bit (do_not_gen, dregno);
+
+ if (!DF_REF_FLAGS_IS_SET (def, DF_REF_PARTIAL |
DF_REF_CONDITIONAL))
+ bitmap_clear_bit (live, dregno);
}
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=327
[Bug libstdc++/32916] file stream error writing large buffers
--- Comment #1 from pcarlini at suse dot de 2007-07-27 17:08 --- We badly need more information about your system and a tescase easier to use: you are allocating on the heap more than 2GB at once! Anyway, actually only 4.1.2 has large file support on selected, linux, platforms, which works, definitely. -- pcarlini at suse dot de changed: What|Removed |Added Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug c++/32346] [4.2/4.3 Regression] long long bitfield passed to int argument incorrectly
--- Comment #6 from mmitchel at gcc dot gnu dot org 2007-07-27 17:13 --- Subject: Bug 32346 Author: mmitchel Date: Fri Jul 27 17:13:29 2007 New Revision: 126986 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126986 Log: PR c++/32346 * call.c (convert_for_arg_passing): Only widen bitfields to their declared types if necessary. PR c++/32346 * g++.dg/expr/bitfield9.C: New test. Added: trunk/gcc/testsuite/g++.dg/expr/bitfield9.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/call.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32346
[Bug middle-end/32749] [4.3 regression]: gfortran.dg/auto_array_1.f90
--- Comment #24 from zadeck at gcc dot gnu dot org 2007-07-27 17:22 --- Subject: Bug 32749 Author: zadeck Date: Fri Jul 27 17:22:14 2007 New Revision: 126987 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126987 Log: 2007-07-26 Kenneth Zadeck <[EMAIL PROTECTED]> PR middle-end/32749 * df-problems.c (df_create_unused_note): Removed do_not_gen parm and the updating of the live and do_not_gen sets. (df_note_bb_compute): Added updating of live and do_not_gen sets for regular defs so that the case of clobber inside conditional call is processed correctly. Modified: trunk/gcc/ChangeLog trunk/gcc/df-problems.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32749
[Bug fortran/32760] Error defining subroutine named PRINT
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2007-07-27 16:53 --- Fixed on 4.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32760
[Bug fortran/32899] [4.3 regresssion] Broken diagnostic for invalid use of .eq. for logicals
--- Comment #3 from kargl at gcc dot gnu dot org 2007-07-27 16:59 --- Subject: Bug 32899 Author: kargl Date: Fri Jul 27 16:59:32 2007 New Revision: 126985 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126985 Log: 2007-07-26 Steven G. Kargl <[EMAIL PROTECTED]> PR fortran/32899 * resolve.c (resolve_operator): Add INTRINSIC_EQ_OS comparison. 2007-07-26 Steven G. Kargl <[EMAIL PROTECTED]> PR fortran/32899 * gfortran.dg/logical_comp.f90: Update dg-error strings. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/logical_comp.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32899
[Bug fortran/32880] User operator & allocatable TYPE components: wrong deallocate
--- Comment #4 from patchapp at dberlin dot org 2007-07-27 17:35 --- Subject: Bug number PR32880 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01998.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32880
[Bug middle-end/32749] [4.3 regression]: gfortran.dg/auto_array_1.f90
--- Comment #26 from zadeck at naturalbridge dot com 2007-07-27 17:33 --- revision 126987 -- zadeck at naturalbridge dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32749
[Bug target/32853] [4.3 regression] failing libjava testcases
--- Comment #3 from debian-gcc at lists dot debian dot org 2007-07-27 18:19 --- Reopened: http://lists.debian.org/debian-glibc/2007/07/msg00346.html: On Thu, Jul 26, 2007 at 09:16:00PM +, [EMAIL PROTECTED] wrote: > +2006-11-30 Jan Kratochvil <[EMAIL PROTECTED]> > + > + * sysdeps/unix/sysv/linux/x86_64/clone.S: Provide CFI for the outermost > + `clone' function to ensure proper unwinding stop of gdb. I don't get it. The changelog entry is for _adding_ the directives and matches the changelog entry in glibc HEAD. This patch removes them. If removing them makes anything better then it's got to be a bug in java's unwinder. -- Daniel Jacobowitz CodeSourcery -- debian-gcc at lists dot debian dot org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32853
[Bug fortran/32905] NAMELIST accepts types with ultimate POINTER components
--- Comment #1 from dfranke at gcc dot gnu dot org 2007-07-27 18:47 --- While I'm working on namelists anyway ... -- dfranke at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |dfranke at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2007-07-27 18:47:06 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32905
[Bug libstdc++/32916] file stream error writing large buffers
--- Comment #3 from satyaakam at yahoo dot co dot in 2007-07-27 18:40 --- its on X86_64 bit box. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug libstdc++/32916] file stream error writing large buffers
--- Comment #4 from pcarlini at suse dot de 2007-07-27 18:43 --- then, assuming everything is ok, you have enough memory, etc, your code works, something is wrong with your specific system and we need more details. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug libstdc++/32916] file stream error writing large buffers
--- Comment #5 from pcarlini at suse dot de 2007-07-27 19:23 --- In any case, just tried your specific testcode on an up to date x86_64-linux machine and the problem cannot be reproduced. Make sure the system where you are trying to install the 4.1.x compiler is up to date as regards glibc and the rest of the toolchain. -- pcarlini at suse dot de changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||WORKSFORME http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32916
[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node
--- Comment #1 from jb at gcc dot gnu dot org 2007-07-27 19:53 --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2007-07/msg02008.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32909
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #12 from rosana07a at gmail dot com 2007-07-27 19:56 --- Thanks gfortran team! -- rosana07a at gmail dot com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8
--- Comment #19 from dominiq at lps dot ens dot fr 2007-07-27 19:34 ---
Subject: Re: [4.3 regression] HUGE(1.0d0) output as
+Infinity on ppc-darwin8
> Hum, I don't see anything in rev. 123623
> (http://gcc.gnu.org/viewcvs?view=rev&revision=123623) that looks too
> suspicious. What would need to be done now, in my opinion, is to:
> 1. check that rev. 123622 passes,
> ...
I cannot say that I am fond of this brute force approach!-(it has to go too far
in the past to look practical). Before that I'ld like to understand what's
going wrong. In the meantime a quick and blind fix is to replace in
libgfortran/libgfortran.h the line
#if defined(HAVE_BROKEN_ISFINITE) || defined(__CYGWIN__)
by
#if defined(HAVE_BROKEN_ISFINITE) || defined(__CYGWIN__) ||
defined(whatever_for_PPC_Darwin)
This fix the failure:
FAIL: gfortran.dg/large_real_kind_2.F90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -O3 -fomit-frame-pointer execution
test
FAIL: gfortran.dg/large_real_kind_2.F90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_2.F90 -Os execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O2 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -g execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 -Os execution test
FAIL: gfortran.fortran-torture/compile/pr32417.f90, "-O" (internal compiler
error)
=== gfortran Summary for unix/-m32 ===
# of expected passes19398
# of unexpected failures17
# of expected failures 9
# of unsupported tests 58
/opt/gcc/darwin_build/gcc/testsuite/gfortran/../../gfortran version 4.3.0
20070720 (experimental)
Now among the many things I don't understand is the following facts.
(1) the following program:
#include
#include
#ifdef HAVE_MATH_H
#include
#endif
#include
int main ()
{
#ifdef isfinite
#ifdef LDBL_MAX
printf("LDBL_MAX is defined\n");
if (!isfinite(LDBL_MAX)) printf("bad long double\n");
#endif
#ifdef DBL_MAX
printf("DBL_MAX is defined\n");
if (!isfinite(DBL_MAX)) printf("bad double\n");
#endif
printf("isfinite defined\n");
#endif
printf("end of test\n");
}
gives:
LDBL_MAX is defined
bad long double
DBL_MAX is defined
isfinite defined
end of test
when compiled with gcc version 4.3.0 20070720 and
LDBL_MAX is defined
DBL_MAX is defined
isfinite defined
end of test
when compiled with gcc version 4.0.1 (Apple Computer, Inc. build 5367)
using gcc?? -DHAVE_MATH_H isfinite_p.c (gcc?? stands for the different
flavors).
By any chance is it possible that libgfortran/configure uses
the system gcc and not xgcc? In that case that would explain
why the broken isfinite is not detected.
(2) From this it seems that isfinite(DBL_MAX) is working.
Why is it not working when writing HUGE(1.0d0)?
Does the writing use long doubles?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841
[Bug fortran/31818] Wrongly accepts namelists with assumed-shape arrays
--- Comment #5 from dfranke at gcc dot gnu dot org 2007-07-27 20:27 --- Try this testcase instead ... subroutine test(cha) implicit none character(len=10) :: cha(1:) ! added lower-bound namelist /z/ cha end subroutine test -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31818
[Bug middle-end/32917] New: make profiledbootstrap fails with coverage mismatch
Tried a make profiledbootstrap with gcc 4.2 branch as of 070727; it failed with ../../gcc/gcc/varasm.c: In function 'default_elf_asm_named_section': ../../gcc/gcc/varasm.c:6227: error: coverage mismatch for function 'default_elf_ asm_named_section' while reading counter 'arcs' ../../gcc/gcc/varasm.c:6227: error: number of counters is 17 instead of 21 ../../gcc/gcc/varasm.c: In function 'default_function_rodata_section': ../../gcc/gcc/varasm.c:6227: error: coverage mismatch for function 'default_func tion_rodata_section' while reading counter 'arcs' ../../gcc/gcc/varasm.c:6227: error: number of counters is 19 instead of 25 make[3]: *** [varasm.o] Error 1 -- Summary: make profiledbootstrap fails with coverage mismatch Product: gcc Version: 4.2.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ak at muc dot de GCC host triplet: x86_64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32917
[Bug libgcj/30071] make install fails for libjava
--- Comment #5 from tromey at gcc dot gnu dot org 2007-07-27 20:11 --- I don't think we should use this particular patch. My reason is that ordering alone is insufficient to guarantee success here, if the user uses "make -j". Instead, explicit dependencies should be used. In addition to fixing the above these might be a bit more resilient (who knows?) when automake changes. See comment #1 for an example; basically an install target for an executable should depend on the needed library install target. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30071
[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2007-07-27 20:40 --- Dominique, I have the same problem as FX. I do not have access to this platform. If I could secure shell (ssh) into one of these, I would work on this. Your idea on the order of #defines is probably on the right track. Jannes patch did tweak the includes somewhat. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841
[Bug debug/31899] [4.2/4.3 regression] -g and using declaration causing ICE in reference_to_unused
--- Comment #5 from dougkwan at google dot com 2007-07-27 20:54 --- Created an attachment (id=13989) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13989&action=view) Proposed fix for SEGV problem in dwarf2out.c in bug 31899 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31899
[Bug target/32915] ICE while compiling libgfortran/io/write.c
-- dannysmith at users dot sourceforge dot net changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |dannysmith at users dot |dot org |sourceforge dot net Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2007-07-27 20:30:51 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32915
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #13 from fxcoudert at gcc dot gnu dot org 2007-07-27 20:51 --- (In reply to comment #12) > Thanks gfortran team! Hum, thanks for the thanks! However, I feel it would be better to keep this open because the code that the front-end previously generated was OK and exposed a real bug in the middle-end, which might come and bite us again later. So, I'm reopening this, unless a middle-end maintainer wants to shut it himself as INVALID or WONTFIX. Also, I'm raising this to priority P1, as is appropriate (if I understand correctly) for a ice-on-valid-code regression. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|RESOLVED|REOPENED GCC build triplet|i686| GCC host triplet|i686| GCC target triplet|i686| Priority|P3 |P1 Resolution|FIXED | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #14 from pinskia at gcc dot gnu dot org 2007-07-27 21:06 --- This is the same bug as PR 32873 so I am going to close it as a dup. *** This bug has been marked as a duplicate of 32873 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|REOPENED|RESOLVED Priority|P1 |P3 Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug tree-optimization/32873] [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-27 21:06 --- *** Bug 32720 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||rosana07a at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32873
[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8
--- Comment #21 from dominiq at lps dot ens dot fr 2007-07-27 21:43 --- Subject: Re: [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8 > Your idea on the order of #defines is probably on the right track. As I said, this is the quickest way to hide the problem. I have tested that it works and it's only the matter to know the equivalent of __CYGWIN__ for powerpc-darwin to implement it. Indeed it won't help to understand the origin of the problem which may resurface in an other context. It would help to have answers to the following questions: (1) why isfinite(DBL_MAX) is working, but not isfinite(HUGE(1.0d0))? Does libfortran convert HUGE(1.0d0) to long double? If not, what's happening? (2) Does configure use the system gcc or xgcc from the latest stage? In the first case, this explain why HAVE_BROKEN_ISFINITE is not defined, but raise the question of the relevance of building gcc through 3 stages while keeping the config at stage 1. I the second case, why HAVE_BROKEN_ISFINITE is not defined? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841
[Bug c++/32346] [4.2/4.3 Regression] long long bitfield passed to int argument incorrectly
--- Comment #7 from mmitchel at gcc dot gnu dot org 2007-07-27 21:46 --- Subject: Bug 32346 Author: mmitchel Date: Fri Jul 27 21:46:33 2007 New Revision: 126999 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126999 Log: PR c++/32346 * call.c (convert_for_arg_passing): Only widen bitfields to their declared types if necessary. PR c++/32346 * g++.dg/expr/bitfield9.C: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/g++.dg/expr/bitfield9.C Modified: branches/gcc-4_2-branch/gcc/cp/ChangeLog branches/gcc-4_2-branch/gcc/cp/call.c branches/gcc-4_2-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32346
[Bug middle-end/32917] make profiledbootstrap fails with coverage mismatch with --disable-checking
--- Comment #1 from ak at muc dot de 2007-07-27 21:50 --- Addendum: it seems to only happen with --disable-checking; with --enable-checking=release it works (for completeness full configure options were --disable-checking --disable-nls --enable-languages=c,c++) -- ak at muc dot de changed: What|Removed |Added Summary|make profiledbootstrap fails|make profiledbootstrap fails |with coverage mismatch |with coverage mismatch with ||--disable-checking http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32917
[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node
--- Comment #2 from jb at gcc dot gnu dot org 2007-07-27 22:32 --- Subject: Bug 32909 Author: jb Date: Fri Jul 27 22:32:20 2007 New Revision: 127003 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127003 Log: 2007-07-28 Janne Blomqvist <[EMAIL PROTECTED]> PR fortran/32909 * trans-stmt.c (gfc_trans_character_select): Replace occurrences of gfc_c_int_type_node with integer_type_node. * trans-decl.c (gfc_build_intrinsic_function_decls): Likewise. (gfc_build_builtin_function_decls): Likewise. (gfc_generate_function_code): Likewise. * trans-io.c (gfc_build_io_library_fndecls): Likewise. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c trunk/gcc/fortran/trans-io.c trunk/gcc/fortran/trans-stmt.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32909
[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node
--- Comment #3 from jb at gcc dot gnu dot org 2007-07-27 22:41 --- Fixed, closing. -- jb at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32909
[Bug testsuite/32471] Testcases which always fail on targets where an int is 16 bits
--- Comment #2 from rask at gcc dot gnu dot org 2007-07-27 23:03 --- Subject: Bug 32471 Author: rask Date: Fri Jul 27 23:03:01 2007 New Revision: 127005 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127005 Log: PR testsuite/32471 * gcc.dg/torture/pr30364-1.c (f)(main): Use INT_MAX instead of assuming it is 0x7. * gcc.dg/torture/pr30364-2.c (f)(main): Likewise. * gcc.dg/torture/pr30364-3.c (f)(main): Likewise. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/torture/pr30364-1.c trunk/gcc/testsuite/gcc.dg/torture/pr30364-2.c trunk/gcc/testsuite/gcc.dg/torture/pr30364-3.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32471
[Bug testsuite/32471] Testcases which always fail on targets where an int is 16 bits
--- Comment #3 from rask at sygehus dot dk 2007-07-27 23:05 --- Fixed as of revision 127005. -- rask at sygehus dot dk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32471
[Bug c/32918] New: segmentation fault
internal error: Segmentation fault This appears to complain about the end of a very long function. mipsisa32-elf-i386-win32/bin/mipsisa32-elf-gcc -c -MD -nostdinc -funsigned-char -Wall -Wno-unused -Wpointer-arith -Wbad-function-cast -Wnested-externs -Winline -Werror -msoft-float -Wsign-compare -Wunused-variable -Wunused-value -ffunction-sections -O2 -fno-for-scope -fno-exceptions -fno-unroll-loops -EB -mips32 -G 0 -w I tried the -save-temps with no luck. If you can provide some instructions, that would be nice. Thanks, Jim -- Summary: segmentation fault Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jshoghli at gmail dot com GCC target triplet: eCos building on win32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32918
[Bug c++/32346] [4.2/4.3 Regression] long long bitfield passed to int argument incorrectly
--- Comment #8 from mmitchel at gcc dot gnu dot org 2007-07-27 23:24 --- Fixed in 4.2.2. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32346
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #15 from rosana07a at gmail dot com 2007-07-27 23:33 --- My problem is solved; the rest is beyond me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug tree-optimization/32720] [4.3 Regression] No coalesce ssa_names
--- Comment #16 from rosana07a at gmail dot com 2007-07-27 23:36 --- My problem is solved; the rest is beyond me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32720
[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8
--- Comment #23 from fxcoudert at gcc dot gnu dot org 2007-07-27 23:46 --- (In reply to comment #22) > So we could fix this by doing the extract_real differently. Let em give this > further thought. I plan to change that in the future, because always converting to the longest floating-point type is probably not efficient. In my opinion, we need specialized versions of this code for each floating-point type, but it requires a bit of clear thinking to minimize code duplication and to ease maintainance. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841
[Bug tree-optimization/32873] [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption
--- Comment #3 from michelin60 at gmail dot com 2007-07-28 00:00 --- Somewhat irritated by this plagiarizing the following come from my earlier PR32865 Unable to coalesce ssa_names 1221 and 144 which are marked as MUST COALESCE. is_long_double_1221(ab) and is_long_double_144(ab) vfprintf.c:184: internal compiler error: SSA corruption Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. --- Comment #1 From [EMAIL PROTECTED] 2007-07-23 13:48 [reply] --- Created an attachment (id=13952) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13952&action=view) [edit] preprocessed vprintf.c from glibc-2.6 vprintf.c from glibc-2.6, glibc2.6.90, and glibc-2.5 differ in minor ways but cause the same SSA-Corruption --- Comment #2 From [EMAIL PROTECTED] 2007-07-23 13:51 [reply] --- Created an attachment (id=13953) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13953&action=view) [edit] Partial *.s output --- Comment #3 From Andrew Pinski 2007-07-23 17:22 [reply] --- Stop changing the CC for this bug, the issue is a generic issue and most likely unrelated to any of the CC you added. This is more likely to be a PRE issue than anything else. When I get into work, I will look into it further to double check. --- Comment #4 From [EMAIL PROTECTED] 2007-07-23 18:03 [reply] --- (In reply to comment #3) > Stop changing the CC for this bug, the issue is a generic issue and most > likely > unrelated to any of the CC you added. This is more likely to be a PRE issue > than anything else. When I get into work, I will look into it further to > double check. > The three person CC'd are listed per MAINTAINERS as follows: rs600o portDavid Edelsohn c++ runtime libs Ulrich Drepper (also glibc) tree-ssa Andrew Macloed while spu port Andre Pinski (spu ?= playsation.sony.???) Doing a search of PR's filed I came up, surprise, with no remotely equivalent report and I chose people that matched what I reported. As the author of the report I think that I have the right to choose peple that match as provided by the MAINTAINER's list --- Comment #5 From David Edelsohn 2007-07-23 18:05 [reply] --- Subject: Re: [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption > michelin60 at gmail dot com writes: michelin60> Doing a search of PR's filed I came up, surprise, with no remotely equivalent michelin60> report and I chose people that matched what I reported. As the author of the michelin60> report I think that I have the right to choose peple that match as provided by michelin60> the MAINTAINER's list No, you do not. You submitted the bug. Let the GCC developers decide how best to triage and analyse the bug. David --- Comment #6 From [EMAIL PROTECTED] 2007-07-23 18:33 [reply] --- (In reply to comment #5) > Subject: Re: [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption > > No, you do not. You submitted the bug. Let the GCC developers > decide how best to triage and analyse the bug. > > David Well David here is an interesting quote: IMO the most notorious case is how the gcc development is held hostage by Edelsohn and maybe IBM as a whole by requesting that everything always works perfectly well on AIX. How often has one seen "this patch breaks AIX, back it out". It cannot reasonably be expected that everybody tests on AIX. It is an proprietary OS running on proprietary and expensive hardware which not many people have access to. The overall development speed could be significantly improved by dropping the AIX requirement which, in some form or another, has been agreed upon by the steering committee. AIX is irrelevant in general today, i.e., the situation changed. And the people in the steering committee are too nice to just tell the very small minority causing the problem to take a hike. --- Comment #7 From Andrew Pinski 2007-07-23 18:42 [reply] --- (In reply to comment #6) > Well David here is an interesting quote: Lets put it this way, this quote is true but it is held hostage in a good way. You don't want broken code in your compiler do you? This is what David and AIX does for GCC, they prevent bad code from being in GCC. Have you looked into what has been found via compiling on AIX? Lots of bugs. Who wants bugs in their compiler? Anyways as I have mentioned before, I am 99% sure this is ___NOT___ related to the powerpc back-end at all. And next time please don't CC anyone unless you are sure at what patch caused the issue. Also don't you can't expect a response within 24 hours, GCC developers are busy with their day jobs. --- Comment #8 From Andrew Pinski 2007-07-23 18:56 [reply] --- Working on a reduced testcase but when I quickly looked into it, PRE was messing up the variables that have abnormal set so this is unrelated to the rs6000 back-end. --- Comment #9 From Andrew Pinski 2007-07-23
[Bug target/32853] [4.3 regression] failing libjava testcases
--- Comment #4 from daney at gcc dot gnu dot org 2007-07-28 00:01 --- Java just uses the unwinder in libgcc_s. The same one that C++ and C use. If it is a problem with the unwinder one might expect to see it in those languages as well. However, it would seem to be somewhat system dependent: http://gcc.gnu.org/ml/gcc-testresults/2007-07/msg01070.html http://gcc.gnu.org/ml/gcc-testresults/2007-07/msg01090.html http://gcc.gnu.org/ml/gcc-testresults/2007-07/msg00995.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32853
[Bug tree-optimization/32873] [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-07-28 00:03 --- > Somewhat irritated by this plagiarizing the following come from my earlier PR32865 Please don't copy the whole older bug in a newer bug please. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32873
[Bug tree-optimization/32919] New: [4.3 Regression] SSA corruption because of abnormal edges and PRE
Unable to coalesce ssa_names 1221 and 144 which are marked as MUST COALESCE.
is_long_double_1221(ab) and is_long_double_144(ab)
vfprintf.c: In function '_IO_vfprintf_internal':
vfprintf.c:184: internal compiler error: SSA corruption
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
Testcase:
void _IO_vfprintf_internal ( char *f )
{
static const void *const step0_jumps[] = { &&do_form_unknown, &&do_flag_plus,
&&do_form_float };
const void * ptr = step0_jumps[0];
do {
char spec;
spec = (*++f);
goto *ptr;
do_flag_plus:
read_int (&f);
do_number:
_itoa_word (spec);
do_form_float:
if (ptr != ((void *)0))
{
spec = 'x';
goto do_number;
}
if (spec != 'S')
__strnlen ();
return;
do_form_unknown:;
}
while (*f != '\0');
}
--
Summary: [4.3 Regression] SSA corruption because of abnormal
edges and PRE
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pinskia at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32919
[Bug tree-optimization/32919] [4.3 Regression] SSA corruption because of abnormal edges and PRE
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-28 00:05 --- Value numbering spec_28(ab) stmt = spec_28(ab) = PHI Setting value number of spec_28(ab) to spec_7(ab) We should not value number this PHI node, yes it is a copy but a needed copy for abnormal edges. Note the reduced testcase is missing an optimization but that is already filed as PR 32810. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||dberlin at gcc dot gnu dot ||org Keywords||ice-on-valid-code Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32919
[Bug tree-optimization/32873] [4.3 Regression] glibc ICE's gcc-4.3.0 SSA corruption
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-07-28 00:05 --- Closing as a dup of the newer 32919 which does not have the rant. *** This bug has been marked as a duplicate of 32919 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32873
[Bug tree-optimization/32919] [4.3 Regression] SSA corruption because of abnormal edges and PRE
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-28 00:05 --- *** Bug 32873 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32919
[Bug target/32918] segmentation fault
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|blocker |normal Component|c |target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32918
[Bug target/32853] [4.3 regression] failing libjava testcases
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-07-28 00:21 --- One should read: http://sourceware.org/ml/gdb/2006-12/msg00100.html And: http://sourceware.org/ml/gdb-patches/2006-12/msg00178.html I don't know if this counts as a GCC bug or a glibc one now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32853
[Bug c/32920] New: error: type mismatch in binary expression
Bootstrap (revision 126993 with gmp and mpfr in tree) fail with the error:
/gcctmp/gcc070727/build/./prev-gcc/xgcc -B/gcctmp/gcc070727/build/./prev-gcc/
-B/usr/local/i386-unknown-netbsdelf3.1/bin/ -DHAVE_CONFIG_H -I.
-I../../../gcc/gmp/printf -I.. -D__GMP_WITHIN_GMP -I../../../gcc/gmp -DNO_ASM
-g -O2 -fomit-frame-pointer -c ../../../gcc/gmp/printf/printffuns.c -o
printffuns.o
../../../gcc/gmp/printf/printffuns.c: In function 'gmp_fprintf_reps':
../../../gcc/gmp/printf/printffuns.c:56: error: type mismatch in binary
expression
unsigned int
int
unsigned int
D.4054 = MIN_EXPR
../../../gcc/gmp/printf/printffuns.c:56: error: type mismatch in binary
expression
unsigned int
int
unsigned int
D.4055 = MIN_EXPR
> ./xgcc -B./ -v
Reading specs from ./specs
Target: i386-unknown-netbsdelf3.1
Configured with: ../gcc/configure --enable-languages=all,treelang,obj-c++
Thread model: posix
gcc version 4.3.0 20070727 (experimental)
A cut down example that reproduce the error:
#define MIN(l,o) ((l) < (o) ? (l) : (o))
int a;
void
foo(void)
{
char buf[10];
a = MIN(a, sizeof (buf));
}
--
Summary: error: type mismatch in binary expression
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: kristerw at gcc dot gnu dot org
GCC build triplet: i386-unknown-netbsdelf3.1
GCC host triplet: i386-unknown-netbsdelf3.1
GCC target triplet: i386-unknown-netbsdelf3.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32920
[Bug tree-optimization/32921] New: [4.3 Regression] Revision 126326 causes 12% slowdown
This checkin: http://gcc.gnu.org/ml/gcc-cvs/2007-07/msg00168.html causes 12% slowdown for 437.leslie3d in SPEC CPU 2006 on 64bit Core 2 Duo when compiled with -O2 -ffast-math. -- Summary: [4.3 Regression] Revision 126326 causes 12% slowdown Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32921
[Bug middle-end/32920] [4.3 Regression] error: type mismatch in binary expression
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Summary|error: type mismatch in |[4.3 Regression] error: type |binary expression |mismatch in binary ||expression Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32920
[Bug tree-optimization/32921] [4.3 Regression] Revision 126326 causes 12% slowdown
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-28 00:32 --- Do you know why? Because right now there is not enough information in this bug to declare if it is a bug or not. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Summary|[4.3 Regression] Revision |[4.3 Regression] Revision |126326 causes 12% slowdown |126326 causes 12% slowdown http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32921
[Bug tree-optimization/32921] [4.3 Regression] Revision 126326 causes 12% slowdown
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-28 00:32 --- Or really a scheduling fuck up in the core 2 duo. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32921
[Bug middle-end/32917] make profiledbootstrap fails with coverage mismatch with --disable-checking
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-28 00:36 --- Usually when --enable-checking=release works but --disable-checking does not, it is due to someone having a gcc_assert with a side effect. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32917
[Bug debug/32914] ICE in rtl_for_decl_init with -g option
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Severity|major |normal http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32914
[Bug debug/32914] [4.2/4.3 Regression] ICE in rtl_for_decl_init with -g option
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-28 00:42 ---
Reduced testcase:
typedef int __m128i __attribute__ ((__vector_size__ (16) ));
const __m128i tmp={0,0};
This is a blocker for everyone using vectors with g++.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |blocker
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
GCC build triplet|x86_64 |
GCC host triplet|x86_64 |
GCC target triplet|x86_64 |dwarf2
Keywords||ice-on-valid-code
Last reconfirmed|-00-00 00:00:00 |2007-07-28 00:42:23
date||
Summary|ICE in rtl_for_decl_init|[4.2/4.3 Regression] ICE in
|with -g option |rtl_for_decl_init with -g
||option
Target Milestone|--- |4.2.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32914
[Bug tree-optimization/32912] [4.3 Regression] ICE with vector code
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-28 00:46 --- This worked in 4.3.0 20070629. Also I doubt it is related to C99 compound literal expressions, just for vectors you need to use them -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Component|c++ |tree-optimization Summary|[Regression] ICE with C99 |[4.3 Regression] ICE with |compound literal expression |vector code Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32912
[Bug bootstrap/32922] New: configure[14052]: assembler: A test command parameter is not valid 14052]: assembler: A test command parameter is not valid
The configure script in the gcc directory is broken: ... checking linker for .hidden support... yes checking assembler for .sleb128 and .uleb128... /test/gnu/gcc/gcc/gcc/configure[ 14052]: assembler: A test command parameter is not valid. yes ... -- Summary: configure[14052]: assembler: A test command parameter is not valid 14052]: assembler: A test command parameter is not valid Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: danglin at gcc dot gnu dot org GCC build triplet: hppa*-*-* GCC host triplet: hppa*-*-* GCC target triplet: hppa*-*-* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32922
[Bug tree-optimization/32921] [4.3 Regression] Revision 126326 causes 12% slowdown
--- Comment #3 from hjl at lucon dot org 2007-07-28 00:51 --- I also saw 13% slowdown on Opteron. It may also happen on other none-x86 processors. This program is in Fortran. It has loops with 3-D, 4-D and 5-D arrays. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32921
[Bug bootstrap/32922] configure[14052]: assembler: A test command parameter is not valid
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-28 00:51 --- >The configure script in the gcc directory is broken: The configure script is broken due to a change of binutils version formating, I think there already exist another bug about this. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Summary|configure[14052]: assembler:|configure[14052]: assembler: |A test command parameter is |A test command parameter is |not valid |not valid |14052]: assembler: A test |14052]: assembler: A test |command parameter is not|command parameter is not |valid |valid http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32922
[Bug bootstrap/32922] configure[14052]: assembler: A test command parameter is not valid
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-28 00:52 --- *** This bug has been marked as a duplicate of 32287 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32922
[Bug bootstrap/32287] gas version style changed causes warnings with configure
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-07-28 00:52 --- *** Bug 32922 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||danglin at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32287
[Bug bootstrap/32287] gas version style changed causes warnings with configure
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-07-28 00:53 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords||build Last reconfirmed|-00-00 00:00:00 |2007-07-28 00:53:45 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32287
[Bug tree-optimization/32921] [4.3 Regression] Revision 126326 causes 12% slowdown
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-07-28 01:02 --- The patch just makes more types be the same inside GCC so if this caused a regression, then this is a latent bug or it is the case where mem-ssa failed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32921
[Bug middle-end/32912] [4.3 Regression] ICE with vector code
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-28 01:15 ---
fold-const.c is causing it at:
10277 /* ~X ^ X is -1. */
The issue is that we don't fold ~vector_cst at all.
Anyways here is a reduced testcase:
typedef int __m128i __attribute__ ((__vector_size__ (16) ));
typedef __m128i v2d;
v2d rval();
v2d g;
struct A {
v2d a;
v2d b;
};
struct B {
A a;
};
void foo(B);
void bar() {
v2d l;
A a={};
a.a ^= ~a.b;
a.a ^= ~(v2d) {0,0};
B c = {a};
foo(c);
}
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Component|tree-optimization |middle-end
Ever Confirmed|0 |1
Last reconfirmed|-00-00 00:00:00 |2007-07-28 01:15:25
date||
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32912
[Bug fortran/32195] [regression] ICE in get_array_ctor_strlen
--- Comment #3 from patchapp at dberlin dot org 2007-07-28 02:05 --- Subject: Bug number PR 32195 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-07/msg02023.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32195
[Bug c/32923] New: [4.3.0 Regression] too many memory references for `lea'
Failing: gcc: warning: -pipe ignored because -save-temps specified Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.3.0/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --disable-nls --disable-multilib --disable-werror --disable-libunwind-exceptions --enable-checking --enable-decimal-float --enable-shared --enable-tls --enable-threads=posix --enable-bootstrap --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran --with-cpu=pentium3 --with-system-zlib Thread model: posix gcc version 4.3.0 20070727 (experimental) /usr/libexec/gcc/i686-pc-linux-gnu/4.3.0/cc1 -E -quiet -nostdinc -v -Iinclude -Iinclude/asm-i386/mach-generic -Iinclude/asm-i386/mach-default -D__KERNEL__ -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(binfmt_misc) -DKBUILD_MODNAME=KBUILD_STR(binfmt_misc) -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/include -include include/linux/autoconf.h -MD fs/.binfmt_misc.o.d fs/binfmt_misc.c -m32 -msoft-float -mregparm=3 -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium3 -maccumulate-outgoing-args -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-aliasing -fno-common -freg-struct-return -ffreestanding -fomit-frame-pointer -fno-stack-protector -O2 -fpch-preprocess -o binfmt_misc.i #include "..." search starts here: #include <...> search starts here: include include/asm-i386/mach-generic include/asm-i386/mach-default /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/include End of search list. /usr/libexec/gcc/i686-pc-linux-gnu/4.3.0/cc1 -fpreprocessed binfmt_misc.i -quiet -dumpbase binfmt_misc.c -m32 -msoft-float -mregparm=3 -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium3 -maccumulate-outgoing-args -auxbase-strip fs/binfmt_misc.o -O2 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Wdeclaration-after-statement -Wno-pointer-sign -version -fno-strict-aliasing -fno-common -freg-struct-return -ffreestanding -fomit-frame-pointer -fno-stack-protector -o binfmt_misc.s GNU C version 4.3.0 20070727 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 4.3.0 20070727 (experimental), GMP version 4.2.1, MPFR version 2.2.1-p5. GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 Compiler executable checksum: ac3ca7e64eba7d5a2817cf1303d13ced /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/../../../../i686-pc-linux-gnu/bin/as -V -Qy -o fs/binfmt_misc.o binfmt_misc.s GNU assembler version 2.17 (i686-pc-linux-gnu) using BFD version 2.17 include/asm/string.h: Assembler messages: include/asm/string.h:177: Error: too many memory references for `lea' Working: gcc: warning: -pipe ignored because -save-temps specified Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.2.2/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-nls --disable-werror --disable-multilib --disable-libunwind-exceptions --enable-shared --enable-threads=posix --enable-bootstrap --enable-ffi --enable-__cxa_atexit --enable-libgcc-math --enable-languages=c,c++,fortran --with-cpu=pentium3 --with-system-zlib --enable-clocale=gnu Thread model: posix gcc version 4.2.1 /usr/libexec/gcc/i686-pc-linux-gnu/4.2.1/cc1 -E -quiet -nostdinc -v -Iinclude -Iinclude/asm-i386/mach-generic -Iinclude/asm-i386/mach-default -D__KERNEL__ -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(binfmt_misc) -DKBUILD_MODNAME=KBUILD_STR(binfmt_misc) -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/include -include include/linux/autoconf.h -MD fs/.binfmt_misc.o.d fs/binfmt_misc.c -m32 -msoft-float -mregparm=3 -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium3 -maccumulate-outgoing-args -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-aliasing -fno-common -freg-struct-return -ffreestanding -fomit-frame-pointer -fno-stack-protector -O2 -fpch-preprocess -o binfmt_misc.i #include "..." search starts here: #include <...> search starts here: include include/asm-i386/mach-generic include/asm-i386/mach-default /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/include End of search list. /usr/libexec/gcc/i686-pc-linux-gnu/4.2.1/cc1 -fpreprocessed binfmt_misc.i -quiet -dumpbase binfmt_misc.c -m32 -msoft-float -mregparm=3 -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium3 -maccumulate-outgoing-args -auxbase-strip fs/binfmt_misc.o -O2 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -Wdeclaration-after-statement -Wno-pointer-sign -version -fno-strict-aliasing -fno-common -freg-struct-return -ffreestanding -fomit-frame-pointer -fno-stack-protector -o binfmt_misc.s GNU C version 4.2.1 (i686-pc-linux-gnu) compiled by GNU C version 4.2.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable check
[Bug c/32923] [4.3.0 Regression] too many memory references for `lea'
--- Comment #1 from rosana07a at gmail dot com 2007-07-28 02:37 --- Created an attachment (id=13990) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13990&action=view) preprocessed *.i file per gcc-4.2.1 is identical to per 4.3.0 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32923
[Bug fortran/32195] [regression] ICE in get_array_ctor_strlen
--- Comment #4 from dannysmith at users dot sourceforge dot net 2007-07-28 02:38 --- (In reply to comment #3) > Subject: Bug number PR 32195 > > A patch for this bug has been added to the patch tracker. > The mailing list url for the patch is > http://gcc.gnu.org/ml/gcc-patches/2007-07/msg02023.html > Dyslexic fingers meant PR 32915. Sorry Danny -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32195
[Bug c/32923] [4.3.0 Regression] too many memory references for `lea'
--- Comment #2 from rosana07a at gmail dot com 2007-07-28 02:39 --- Created an attachment (id=13991) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13991&action=view) *.s file failing -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32923
[Bug c/32923] [4.3.0 Regression] too many memory references for `lea'
--- Comment #3 from rosana07a at gmail dot com 2007-07-28 02:39 --- Created an attachment (id=13992) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13992&action=view) *.s OK -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32923
[Bug target/32915] ICE while compiling libgfortran/io/write.c
--- Comment #1 from patchapp at dberlin dot org 2007-07-28 02:45 --- Subject: Bug number PR 32915 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-07/msg02024.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32915
[Bug fortran/32880] User operator & allocatable TYPE components: wrong deallocate
--- Comment #5 from pault at gcc dot gnu dot org 2007-07-28 05:29 --- Subject: Bug 32880 Author: pault Date: Sat Jul 28 05:29:06 2007 New Revision: 127011 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127011 Log: 2007-07-28 Paul Thomas <[EMAIL PROTECTED]> PR fortran/32880 * trans-expr.c (gfc_trans_scalar_assign): Revert to fixed order for lse and rse pre expressions, for derived types with allocatable components. Instead, assign the lhs to a temporary and deallocate after the assignment. 2007-07-28 Paul Thomas <[EMAIL PROTECTED]> PR fortran/32880 * gfortran.dg/alloc_comp_assign_6.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/alloc_comp_assign_6.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-expr.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32880
[Bug fortran/32880] User operator & allocatable TYPE components: wrong deallocate
--- Comment #6 from pault at gcc dot gnu dot org 2007-07-28 05:30 --- Fixed on trunk and IVS testsuite gives a clean sweep of greens - yipee! Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32880
