[Bug c++/30080] incorrect code generation, possibly related to casting/aliasing
--- Comment #6 from irving at cs dot stanford dot edu 2006-12-10 02:41 --- (In reply to comment #5) > FC's 4.1.1 is really 4.1.2+plus some 4.2 patches. Yep. I verified again that the bug does occur on x86_x6 with a freshly downloaded version of 4.1.1. It does not occur on i686 with either real 4.1.1 or fc 4.1.1. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30080
[Bug tree-optimization/30126] [4.3 Regression] ICE genautomata.c:6060
--- Comment #7 from pinskia at gmail dot com 2006-12-10 01:25 --- Subject: Re: [4.3 Regression] ICE genautomata.c:6060 On Sun, 2006-12-10 at 01:19 +, amacleod at redhat dot com wrote: > > --- Comment #6 from amacleod at redhat dot com 2006-12-10 01:19 --- > >>Fail in make bootstrap on FC6. > >>Starting on r119634 through at least r119668. > > The TER patch pinskia mentions didn't go in until revision 119657 If my notes > are correct (they could be wrong)... so that couldn't cause a problem in > r119634 > > I will take a peek when I get a chance to see if it was me however. Sorry about that, I miss read what Ben wrote, I thought he had mentioned it worked with r119634 but no longer with r119668. Sorry again, Andrew Pinski -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30126
[Bug tree-optimization/30126] [4.3 Regression] ICE genautomata.c:6060
--- Comment #6 from amacleod at redhat dot com 2006-12-10 01:19 --- >>Fail in make bootstrap on FC6. >>Starting on r119634 through at least r119668. The TER patch pinskia mentions didn't go in until revision 119657 If my notes are correct (they could be wrong)... so that couldn't cause a problem in r119634 I will take a peek when I get a chance to see if it was me however. Andrew -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30126
[Bug tree-optimization/30126] [4.3 Regression] ICE genautomata.c:6060
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-12-09 23:47 --- The only patch in that revision frame that could have cause this (as the others are all target specific patches): +2006-12-08 Andrew MacLeod <[EMAIL PROTECTED]> + + * Makefile.in: Add new file tree-ssa-ter.c. + * tree-outof-ssa.c (struct temp_expr_table_d, new_temp_expr_table, + free_temp_expr_table, add_value_to_version_list, -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||amacleod at redhat dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30126
[Bug middle-end/30095] ICE in lhd_set_decl_assembler_name, at langhooks.c:165 with "-O0"
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-09 22:59 --- We have a CONST_DECL. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Component|fortran |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30095
[Bug c++/30080] incorrect code generation, possibly related to casting/aliasing
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-12-09 22:55 --- (In reply to comment #4) > The default version of gcc 4.1.1 from fedora works. The version > that breaks is a separate build of the compiler with different > configuration options. g++ -v from the fedora version follows. > Do you know any way I could isolate the difference? FC's 4.1.1 is really 4.1.2+plus some 4.2 patches. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30080
[Bug target/30082] Expansion of ceil and floor could use if-conversion
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-09 22:52 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 22:52:53 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30082
[Bug target/30067] use of thread local storage causes code generator to fail
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-09 22:48 --- Fixed for 4.0.0. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30067
[Bug rtl-optimization/30065] Could use indexed addressing to reduce const costs
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-09 22:44 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 22:44:47 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30065
[Bug c/30063] It would be useful for __attribute__((deprecated)) to take an optional parameter
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-09 22:43 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Component|middle-end |c Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 22:43:35 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30063
[Bug target/26968] [4.1 Regression] HDF5 1.7.52 test segfaults with 4.1.0, fine with 4.0.2 (regression)
--- Comment #10 from pinskia at gcc dot gnu dot org 2006-12-09 22:40 --- No testcase in over 3 months so closing. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26968
[Bug other/28297] GCC 4.1.1 fails to build on Mac OS X 10.4.6
--- Comment #12 from pinskia at gcc dot gnu dot org 2006-12-09 22:39 --- This works for me and many others, I wonder if your machine messed up the tar ball and not untar all the sources. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28297
[Bug c++/28986] Failure to diagnose overflow in constant expression
--- Comment #5 from manu at gcc dot gnu dot org 2006-12-09 21:51 --- Why is this "accepts-invalid"? Shouldn't it be "diagnostic" instead? I am trying to understand what is the expected output here: a warning or a pedantic error? -- manu at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2006-12-01 23:36:32 |2006-12-09 21:51:31 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28986
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #6 from andreast at gcc dot gnu dot org 2006-12-09 21:43 --- Bah, the attached patch is now under test, i?86-*darwin*, it refuses to configure for x86_64-*darwin*. So I guess it will not configure libffi under powerpc64-*darwin* either. -- andreast at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |andreast at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2006-12-09 21:03:56 |2006-12-09 21:43:26 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug fortran/25818] Problem with handling optional and entry master arguments
--- Comment #19 from pault at gcc dot gnu dot org 2006-12-09 21:42 --- Promises, promises... > > It is regtesting as I write; if all is well, I will submit tonight with a > testcase based on pr30025. > I'll come to this just as soon as the interface stuff is a bit more sorted. - like next weekend. Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25818
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #5 from andreast at gcc dot gnu dot org 2006-12-09 21:41 --- Created an attachment (id=12776) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12776&action=view) patch -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #4 from andreast at gcc dot gnu dot org 2006-12-09 21:20
---
For the time being, this one, on the previous revision would have been the
better approach. NOTE, it's untested!
[wolfram:gcc/head/gcc] andreast% svn diff configure.in
Index: configure.in
===
--- configure.in(revision 119677)
+++ configure.in(working copy)
@@ -368,7 +368,7 @@
*-*-chorusos)
noconfigdirs="$noconfigdirs target-newlib target-libgloss ${libgcj}"
;;
- powerpc-*-darwin*)
+ powerpc-*-darwin* | i[[3456789]]86-*-darwin*)
noconfigdirs="$noconfigdirs bfd binutils ld gas opcodes gdb gprof"
noconfigdirs="$noconfigdirs sim target-rda"
;;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug fortran/30096] Interface bug: gfortran falsely detect ambigious interface, scoping problem?
--- Comment #6 from pault at gcc dot gnu dot org 2006-12-09 21:13 --- Subject: Bug 30096 Author: pault Date: Sat Dec 9 21:13:29 2006 New Revision: 119697 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119697 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 PR fortran/30096 * interface.c (compare_type_rank_if): Reject invalid generic interfaces. (check_interface1): Give a warning for nonreferred to ambiguous interfaces. (check_sym_interfaces): Check whether an ambiguous interface is referred to. Do not check host associated interfaces since these cannot be ambiguous with the local versions. (check_uop_interface, gfc_check_interfaces): Update call to check_interface1. * symbol.c (gfc_get_sym_tree, gfc_get_sym_tree): Allow adding unambiguous procedures to generic interfaces. * gfortran.h (symbol_attribute): Added use_only and ambiguous_interfaces. * module.c (load_need): Set the use_only flag, if needed. * resolve.c (resolve_fl_procedure): Warn for nonreferred interfaces. * expr.c (find_array_section): Fix initializer array contructor. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Tobias Burnus <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 * gfortran.dg/interface_4.f90: Test adding procedure to generic interface. * gfortran.dg/interface_5.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_6.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_7.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_8.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_1.f90: Change dg-error into a dg-warning. * gfortran.dg/array_initializer_2.f90: Add initializer array constructor test. PR fortran/30096 * gfortran.dg/interface_9.f90: Test that host interfaces are not checked for ambiguity with the local version. Added: trunk/gcc/testsuite/gfortran.dg/interface_4.f90 trunk/gcc/testsuite/gfortran.dg/interface_5.f90 trunk/gcc/testsuite/gfortran.dg/interface_6.f90 trunk/gcc/testsuite/gfortran.dg/interface_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_8.f90 trunk/gcc/testsuite/gfortran.dg/interface_9.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/expr.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/interface.c trunk/gcc/fortran/module.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/array_initializer_2.f90 trunk/gcc/testsuite/gfortran.dg/generic_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30096
[Bug fortran/30068] Ambigous interfaces not detected
--- Comment #13 from pault at gcc dot gnu dot org 2006-12-09 21:13 --- Subject: Bug 30068 Author: pault Date: Sat Dec 9 21:13:29 2006 New Revision: 119697 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119697 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 PR fortran/30096 * interface.c (compare_type_rank_if): Reject invalid generic interfaces. (check_interface1): Give a warning for nonreferred to ambiguous interfaces. (check_sym_interfaces): Check whether an ambiguous interface is referred to. Do not check host associated interfaces since these cannot be ambiguous with the local versions. (check_uop_interface, gfc_check_interfaces): Update call to check_interface1. * symbol.c (gfc_get_sym_tree, gfc_get_sym_tree): Allow adding unambiguous procedures to generic interfaces. * gfortran.h (symbol_attribute): Added use_only and ambiguous_interfaces. * module.c (load_need): Set the use_only flag, if needed. * resolve.c (resolve_fl_procedure): Warn for nonreferred interfaces. * expr.c (find_array_section): Fix initializer array contructor. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Tobias Burnus <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 * gfortran.dg/interface_4.f90: Test adding procedure to generic interface. * gfortran.dg/interface_5.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_6.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_7.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_8.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_1.f90: Change dg-error into a dg-warning. * gfortran.dg/array_initializer_2.f90: Add initializer array constructor test. PR fortran/30096 * gfortran.dg/interface_9.f90: Test that host interfaces are not checked for ambiguity with the local version. Added: trunk/gcc/testsuite/gfortran.dg/interface_4.f90 trunk/gcc/testsuite/gfortran.dg/interface_5.f90 trunk/gcc/testsuite/gfortran.dg/interface_6.f90 trunk/gcc/testsuite/gfortran.dg/interface_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_8.f90 trunk/gcc/testsuite/gfortran.dg/interface_9.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/expr.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/interface.c trunk/gcc/fortran/module.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/array_initializer_2.f90 trunk/gcc/testsuite/gfortran.dg/generic_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30068
[Bug fortran/29975] [meta-bugs] ICEs with CP2K
--- Comment #28 from pault at gcc dot gnu dot org 2006-12-09 21:13 --- Subject: Bug 29975 Author: pault Date: Sat Dec 9 21:13:29 2006 New Revision: 119697 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119697 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 PR fortran/30096 * interface.c (compare_type_rank_if): Reject invalid generic interfaces. (check_interface1): Give a warning for nonreferred to ambiguous interfaces. (check_sym_interfaces): Check whether an ambiguous interface is referred to. Do not check host associated interfaces since these cannot be ambiguous with the local versions. (check_uop_interface, gfc_check_interfaces): Update call to check_interface1. * symbol.c (gfc_get_sym_tree, gfc_get_sym_tree): Allow adding unambiguous procedures to generic interfaces. * gfortran.h (symbol_attribute): Added use_only and ambiguous_interfaces. * module.c (load_need): Set the use_only flag, if needed. * resolve.c (resolve_fl_procedure): Warn for nonreferred interfaces. * expr.c (find_array_section): Fix initializer array contructor. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Tobias Burnus <[EMAIL PROTECTED]> PR fortran/29975 PR fortran/30068 * gfortran.dg/interface_4.f90: Test adding procedure to generic interface. * gfortran.dg/interface_5.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_6.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_7.f90: Test invalid, ambiguous interface. * gfortran.dg/interface_8.f90: Test warning for not-referenced-to ambiguous interfaces. * gfortran.dg/interface_1.f90: Change dg-error into a dg-warning. * gfortran.dg/array_initializer_2.f90: Add initializer array constructor test. PR fortran/30096 * gfortran.dg/interface_9.f90: Test that host interfaces are not checked for ambiguity with the local version. Added: trunk/gcc/testsuite/gfortran.dg/interface_4.f90 trunk/gcc/testsuite/gfortran.dg/interface_5.f90 trunk/gcc/testsuite/gfortran.dg/interface_6.f90 trunk/gcc/testsuite/gfortran.dg/interface_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_8.f90 trunk/gcc/testsuite/gfortran.dg/interface_9.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/expr.c trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/interface.c trunk/gcc/fortran/module.c trunk/gcc/fortran/resolve.c trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/array_initializer_2.f90 trunk/gcc/testsuite/gfortran.dg/generic_7.f90 trunk/gcc/testsuite/gfortran.dg/interface_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #3 from andreast at gcc dot gnu dot org 2006-12-09 21:03 --- Ok, in terms of configuration you are correct, this is a new bug. And the patch which introduced this is here: http://gcc.gnu.org/ml/gcc-cvs/2006-12/msg00297.html -- andreast at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 21:03:56 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug fortran/29464] problem with duplicate USE, ONLY of procedure in INTERFACE
--- Comment #4 from pault at gcc dot gnu dot org 2006-12-09 20:52 --- Subject: Bug 29464 Author: pault Date: Sat Dec 9 20:52:27 2006 New Revision: 119696 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119696 Log: 2006-11-25 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29464 * module.c (load_generic_interfaces): Add symbols for all the local names of an interface. Share the interface amongst the symbols. * gfortran.h : Add generic_copy to symbol_attribute. * symbol.c (free_symbol): Only free interface if generic_copy is not set. 2006-11-25 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29464 * gfortran.dg/module_interface_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/module_interface_2.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/module.c trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29464
[Bug fortran/29941] gfortran reports error with len of assumed size character array
--- Comment #4 from pault at gcc dot gnu dot org 2006-12-09 20:42 --- Subject: Bug 29941 Author: pault Date: Sat Dec 9 20:41:51 2006 New Revision: 119695 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119695 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29941 * resolve.c (resolve_function): Add LEN to the functions not checked for assumed size actual args. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29941 * gfortran.dg/assumed_len.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/assumed_len.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29941
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #2 from lucier at math dot purdue dot edu 2006-12-09 20:27 --- This is not the same bug as 21952. Before, bootstrap would succeed and there would be a lot of test errors. Now, as of the past few days, bootstrap fails. This is a configure bug. -- lucier at math dot purdue dot edu changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug bootstrap/30134] Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
--- Comment #1 from andreast at gcc dot gnu dot org 2006-12-09 20:23 --- *** This bug has been marked as a duplicate of 29152 *** -- andreast at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug libffi/29152] 64-bit darwin ppc port needed for libffi
--- Comment #3 from andreast at gcc dot gnu dot org 2006-12-09 20:23 --- *** Bug 30134 has been marked as a duplicate of this bug. *** -- andreast at gcc dot gnu dot org changed: What|Removed |Added CC||lucier at math dot purdue ||dot edu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29152
[Bug libfortran/26893] kinds.h not generated, causing failure
--- Comment #25 from jbuck at gcc dot gnu dot org 2006-12-09 20:11 --- Jerry: no, gmp isn't in the default path, which is why gcc was configured with --with-gmp and --with-mpfr flags. On this particular machine I do not have root, and since it's used to build apps for legacy systems it has to keep running a rather old and unmodified version of Solaris. The point is that different parts of gcc appear to be inconsistent about whether the --with-gmp flag is adequate, or whether an LD_LIBRARY_PATH setting is also needed. As I said, I fixed the problem by setting LD_LIBRARY_PATH. But I still have an issue over whether this should be required, given the --with-gmp setting and that the configure script detected gmp and even built and ran a test program. Perhaps the gcc list is the best place to discuss this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26893
[Bug other/29639] [4.3 regression] ext/bitmap_allocator/check_allocate_max_size.cc execution test
--- Comment #52 from ebotcazou at gcc dot gnu dot org 2006-12-09 19:48 --- > The errors go away if I disable HAVE_LD_EH_GC_SECTIONS. Sure, see comment #3. > I think this feature exposes a binutils in handling pc-relative > relocations when this feature is enabled. In particulary, it > appears the offset to the lsda data is wrong. OK. Then I'll submit the binutils patch for !HAVE_COMDAT_GROUP and tweak the configury so as to enable the feature only with a fixed linker and not on PA. Thanks for the patch and your help. -- ebotcazou at gcc dot gnu dot org changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639
[Bug middle-end/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #8 from pinskia at gcc dot gnu dot org 2006-12-09 19:36 --- I now have a fix for both issues (fixing the first problem of ineffient gimplification is enough to fix this bug but might not be enough to fix others). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug other/29639] [4.3 regression] ext/bitmap_allocator/check_allocate_max_size.cc execution test
--- Comment #51 from danglin at gcc dot gnu dot org 2006-12-09 19:34 --- Created an attachment (id=12775) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12775&action=view) File. The errors go away if I disable HAVE_LD_EH_GC_SECTIONS. I think this feature exposes a binutils in handling pc-relative relocations when this feature is enabled. In particulary, it appears the offset to the lsda data is wrong. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639
[Bug middle-end/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-12-09 19:24 --- The second issue (the invalid gimple), comes from marking a variable as ADDRESSABLE late after the orginal gimplification to that variable had happened: /* Mark the RHS addressable. */ lang_hooks.mark_addressable (TREE_OPERAND (expr, 0)); -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug middle-end/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-09 19:11 ---
We have:
if ((fallback & fb_lvalue) == 0)
{
result = tmp2 = tmp = create_tmp_var (TREE_TYPE (expr), "iftmp");
ret = GS_ALL_DONE;
}
But fallback is "fallback=fb_either" so the above if is false.
So we have two problems, an ineffient gimplification and a gimplification that
is wrong.
The ineffient gimplification is easy to fix. I will now go to figure out why
we get an invalid one.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |pinskia at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug bootstrap/30134] New: Bootstrap error: "libffi has not been ported to powerpc64-apple-darwin8.8.0"
With this configure and build:
[descartes:gcc/mainline/objdir] gcc-test% cat ../build-and-check-gcc
#!/bin/tcsh
/bin/rm -rf *; env CC=/pkgs/gcc-4.2.0-64/bin/gcc ../configure
--build=powerpc64-apple-darwin8.8.0 --host=powerpc64-apple-darwin8.8.0
--target=powerpc64-apple-darwin8.8.0 --with-gmp=/pkgs/gmp-4.2.1-64/
--with-mpfr=/pkgs/gmp-4.2.1-64/ --prefix=/pkgs/gcc-4.3.0-64; make -j 4
bootstrap BOOT_LDFLAGS='-Wl,-search_paths_first' >& build.log && (make install)
&& (make -k -j 8 check RUNTESTFLAGS="--target_board 'unix{-mcpu=970/-m64}'" >&
check.log ; make mail-report-with-warnings.log)
bootstrap fails with
configure: error: "libffi has not been ported to powerpc64-apple-darwin8.8.0."
make[1]: *** [configure-target-libffi] Error 1
make: *** [bootstrap] Error 2
--
Summary: Bootstrap error: "libffi has not been ported to
powerpc64-apple-darwin8.8.0"
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: lucier at math dot purdue dot edu
GCC build triplet: powerpc64-apple-darwin8.8.0
GCC host triplet: powerpc64-apple-darwin8.8.0
GCC target triplet: powerpc64-apple-darwin8.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30134
[Bug fortran/30115] allocate() interface pessimizes aliasing
--- Comment #8 from tkoenig at gcc dot gnu dot org 2006-12-09 19:03 --- (In reply to comment #7) > I guess it may work to only change > > void allocate (void **, size_t, int *) > to > > void *allocate (void *, size_t, int *) > and use it like > descriptor.data = allocate (descriptor.data, size, pstat) Sounds good. Who'll write the patch? :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30115
[Bug libfortran/26893] kinds.h not generated, causing failure
--- Comment #24 from jvdelisle at verizon dot net 2006-12-09 18:45 --- Subject: Re: kinds.h not generated, causing failure jbuck at gcc dot gnu dot org wrote: > --- Comment #23 from jbuck at gcc dot gnu dot org 2006-12-09 18:14 > --- > > Anyway, the Fortran library built and the compiler is now running tests. > > Whether this one is a true bug is debatable. Have you looked at /etc/ld.so.conf or equivalent on your system? Usually LD_LIBRARY_PATH is needed if the library is not in one of your regular system library paths. You could add it here as well. For example on my system here: $ ldd ./bin/gfc libgmp.so.3 => /usr/lib/libgmp.so.3 (0x003f9d40) libc.so.6 => /lib64/libc.so.6 (0x00312280) /lib64/ld-linux-x86-64.so.2 (0x00312180) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26893
[Bug c++/29731] [4.0/4.1/4.2/4.3 regression] ICE with statement expression as template parameter
--- Comment #2 from patchapp at dberlin dot org 2006-12-09 18:35 --- Subject: Bug number PR c++/29731 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/2006-12/msg00628.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29731
[Bug libfortran/26893] kinds.h not generated, causing failure
--- Comment #23 from jbuck at gcc dot gnu dot org 2006-12-09 18:14 --- I went and rebuilt everything, ran into the problem again, and determined that it was because, although there was a correct --with-gmp, gfortran was failing because gmp wasn't on LD_LIBRARY_PATH. But gmp is now in the middle-end, right? And libstdc++ successfully built with this flow, so the bug isn't encountered for hours on a slow Sparc with -j1. Anyway, the Fortran library built and the compiler is now running tests. Whether this one is a true bug is debatable. It seems to me that every other GNU tool I try, as well as the rest of gcc, builds correctly when the location of a library is given with a --with flag, even if it isn't on LD_LIBRARY_PATH. If this is the GNU standard way, then we have a real bug here. If not, we need loud warnings in the installation instructions that --with-gmp does not suffice. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26893
[Bug fortran/29912] [4.1 only] Gfortran: string array functions behaving incorrectly...
--- Comment #12 from pault at gcc dot gnu dot org 2006-12-09 17:48 --- Subject: Bug 29912 Author: pault Date: Sat Dec 9 17:47:45 2006 New Revision: 119694 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119694 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. PR fortran/29820 * trans-array.c (gfc_get_derived_type): Once done, spread the backend_decl to all identical derived types in all sibling namespaces. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. PR fortran/29820 * gfortran.dg/used_types_13.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/used_types_13.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/expr.c branches/gcc-4_1-branch/gcc/fortran/resolve.c branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-expr.c branches/gcc-4_1-branch/gcc/fortran/trans-types.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29912
[Bug fortran/29821] [4.1 only] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:666ans-types.c:666
--- Comment #10 from pault at gcc dot gnu dot org 2006-12-09 17:48 --- Subject: Bug 29821 Author: pault Date: Sat Dec 9 17:47:45 2006 New Revision: 119694 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119694 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. PR fortran/29820 * trans-array.c (gfc_get_derived_type): Once done, spread the backend_decl to all identical derived types in all sibling namespaces. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. PR fortran/29820 * gfortran.dg/used_types_13.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/used_types_13.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/expr.c branches/gcc-4_1-branch/gcc/fortran/resolve.c branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-expr.c branches/gcc-4_1-branch/gcc/fortran/trans-types.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29821
[Bug fortran/29820] ICE in fold_convert, at fold-const.c:2146
--- Comment #12 from pault at gcc dot gnu dot org 2006-12-09 17:48 --- Subject: Bug 29820 Author: pault Date: Sat Dec 9 17:47:45 2006 New Revision: 119694 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119694 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. PR fortran/29820 * trans-array.c (gfc_get_derived_type): Once done, spread the backend_decl to all identical derived types in all sibling namespaces. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. PR fortran/29820 * gfortran.dg/used_types_13.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/used_types_13.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/expr.c branches/gcc-4_1-branch/gcc/fortran/resolve.c branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-expr.c branches/gcc-4_1-branch/gcc/fortran/trans-types.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29820
[Bug fortran/29916] [4.1 only] Dimension of a function result as host association does not work
--- Comment #11 from pault at gcc dot gnu dot org 2006-12-09 17:48 --- Subject: Bug 29916 Author: pault Date: Sat Dec 9 17:47:45 2006 New Revision: 119694 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119694 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. PR fortran/29820 * trans-array.c (gfc_get_derived_type): Once done, spread the backend_decl to all identical derived types in all sibling namespaces. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. PR fortran/29820 * gfortran.dg/used_types_13.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/used_types_13.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/expr.c branches/gcc-4_1-branch/gcc/fortran/resolve.c branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-expr.c branches/gcc-4_1-branch/gcc/fortran/trans-types.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29916
[Bug fortran/30003] [4.1 only] Expressions with side effects in array references
--- Comment #12 from pault at gcc dot gnu dot org 2006-12-09 17:48 --- Subject: Bug 30003 Author: pault Date: Sat Dec 9 17:47:45 2006 New Revision: 119694 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119694 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. PR fortran/29820 * trans-array.c (gfc_get_derived_type): Once done, spread the backend_decl to all identical derived types in all sibling namespaces. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. PR fortran/29820 * gfortran.dg/used_types_13.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/used_types_13.f90 Modified: branches/gcc-4_1-branch/gcc/fortran/ChangeLog branches/gcc-4_1-branch/gcc/fortran/expr.c branches/gcc-4_1-branch/gcc/fortran/resolve.c branches/gcc-4_1-branch/gcc/fortran/trans-array.c branches/gcc-4_1-branch/gcc/fortran/trans-expr.c branches/gcc-4_1-branch/gcc/fortran/trans-types.c branches/gcc-4_1-branch/gcc/fortran/trans.h branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30003
[Bug fortran/30003] [4.1 only] Expressions with side effects in array references
--- Comment #11 from pault at gcc dot gnu dot org 2006-12-09 15:22 --- Fixed in trunk and 4.2. If I have time, I will patch 4.1 someday. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Summary|[4.2 and 4.1 only] |[4.1 only] Expressions with |Expressions with side |side effects in array |effects in array references |references http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30003
[Bug fortran/29916] [4.1 only] Dimension of a function result as host association does not work
--- Comment #10 from pault at gcc dot gnu dot org 2006-12-09 15:21 --- Fixed in trunk and 4.2. If I have time, I will patch 4.1 someday. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Summary|[4.1 and 4.2 only] Dimension|[4.1 only] Dimension of a |of a function result as host|function result as host |association does not work |association does not work http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29916
[Bug fortran/29912] [4.1 only] Gfortran: string array functions behaving incorrectly...
--- Comment #11 from pault at gcc dot gnu dot org 2006-12-09 15:21 --- Fixed in trunk and 4.2. If I have time, I will patch 4.1 someday. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Summary|[4.2 and 4.1 only] Gfortran:|[4.1 only] Gfortran: string |string array functions |array functions behaving |behaving incorrectly... |incorrectly... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29912
[Bug fortran/29821] [4.1 only] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:666ans-types.c:666
--- Comment #9 from pault at gcc dot gnu dot org 2006-12-09 15:20 --- Fixed in trunk and 4.2. If I have time, I will patch 4.1 someday. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Summary|[4.2 and 4.1] ICE in|[4.1 only] ICE in |gfc_typenode_for_spec, at |gfc_typenode_for_spec, at |fortran/trans- |fortran/trans- |types.c:666ans-types.c:666 |types.c:666ans-types.c:666 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29821
[Bug fortran/29821] [4.2 and 4.1] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:666ans-types.c:666
--- Comment #8 from pault at gcc dot gnu dot org 2006-12-09 15:17 --- Subject: Bug 29821 Author: pault Date: Sat Dec 9 15:17:16 2006 New Revision: 119690 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119690 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_array_transpose): Likewise. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/expr.c branches/gcc-4_2-branch/gcc/fortran/resolve.c branches/gcc-4_2-branch/gcc/fortran/trans-array.c branches/gcc-4_2-branch/gcc/fortran/trans-expr.c branches/gcc-4_2-branch/gcc/fortran/trans.h branches/gcc-4_2-branch/gcc/testsuite/ChangeLog branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/allocatable_function_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29821
[Bug fortran/29912] [4.2 and 4.1 only] Gfortran: string array functions behaving incorrectly...
--- Comment #10 from pault at gcc dot gnu dot org 2006-12-09 15:17 --- Subject: Bug 29912 Author: pault Date: Sat Dec 9 15:17:16 2006 New Revision: 119690 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119690 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_array_transpose): Likewise. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/expr.c branches/gcc-4_2-branch/gcc/fortran/resolve.c branches/gcc-4_2-branch/gcc/fortran/trans-array.c branches/gcc-4_2-branch/gcc/fortran/trans-expr.c branches/gcc-4_2-branch/gcc/fortran/trans.h branches/gcc-4_2-branch/gcc/testsuite/ChangeLog branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/allocatable_function_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29912
[Bug fortran/30003] [4.2 and 4.1 only] Expressions with side effects in array references
--- Comment #10 from pault at gcc dot gnu dot org 2006-12-09 15:17 --- Subject: Bug 30003 Author: pault Date: Sat Dec 9 15:17:16 2006 New Revision: 119690 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119690 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_array_transpose): Likewise. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/expr.c branches/gcc-4_2-branch/gcc/fortran/resolve.c branches/gcc-4_2-branch/gcc/fortran/trans-array.c branches/gcc-4_2-branch/gcc/fortran/trans-expr.c branches/gcc-4_2-branch/gcc/fortran/trans.h branches/gcc-4_2-branch/gcc/testsuite/ChangeLog branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/allocatable_function_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30003
[Bug fortran/29916] [4.1 and 4.2 only] Dimension of a function result as host association does not work
--- Comment #9 from pault at gcc dot gnu dot org 2006-12-09 15:17 --- Subject: Bug 29916 Author: pault Date: Sat Dec 9 15:17:16 2006 New Revision: 119690 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119690 Log: 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> Backports from trunk PR fortran/29821 * resolve.c (resolve_operator): Only return result of gfc_simplify_expr if expression is constant. PR fortran/29912 * trans-expr.c (gfc_trans_arrayfunc_assign): Return NULL if the lhs and rhs character lengths are not constant and equal for character array valued functions. PR fortran/29916 * resolve.c (resolve_symbol): Allow host-associated variables in the specification expression of an array-valued function. * expr.c (check_restricted): Accept host-associated dummy array indices. PR fortran/30003 * trans-array.c (gfc_trans_create_temp_array): Set the section ends to zero. (gfc_conv_array_transpose): Likewise. (gfc_conv_section_startstride): Declare an expression for end, set it from a the array reference and evaluate it for the info structure. Zero the ends in the ss structure and set end, used in the bounds check, from the info structure. trans.h: Add and end array to the gfc_ss_info structure. 2006-12-09 Paul Thomas <[EMAIL PROTECTED]> PR fortran/29821 * gfortran.dg/parameter_array_section_1.f90: New test. PR fortran/29912 * gfortran.dg/char_result_12.f90: New test. PR fortran/29916 * gfortran.dg/host_dummy_index_1.f90: Added additional test. PR fortran/30003 * gfortran.dg/allocatable_function_1.f90: Increase the number of expected calls of free to 10; the lhs section reference is now evaluated so there is another call to bar. Change the comment appropriately. * gfortran.dg/array_section_1.f90: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/array_section_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/char_result_12.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/parameter_array_section_1.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/expr.c branches/gcc-4_2-branch/gcc/fortran/resolve.c branches/gcc-4_2-branch/gcc/fortran/trans-array.c branches/gcc-4_2-branch/gcc/fortran/trans-expr.c branches/gcc-4_2-branch/gcc/fortran/trans.h branches/gcc-4_2-branch/gcc/testsuite/ChangeLog branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/allocatable_function_1.f90 branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/host_dummy_index_1.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29916
[Bug target/30131] ICE in propagate_one_insn, at flow.c:1583
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-12-09 15:11 --- Related to PR28282 and PR12535. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added BugsThisDependsOn||12535 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30131
[Bug tree-optimization/30105] reassoc can sometimes get in the way of PRE
--- Comment #5 from dberlin at gcc dot gnu dot org 2006-12-09 15:06 --- (In reply to comment #1) > Confirmed (but it's not PRE). > This actually is a case of PRE, because data[0] + data[3] is partially redundant. But according to the results, we *did* do the load PRE here. In fact, PRE does the address calculation elimination too. Replaced *data_3 with prephitmp.26_35 in D.1635_18 = *data_3; Replaced data_3 + 12B with prephitmp.24_33 in D.1636_19 = data_3 + 12B; Replaced *D.1636_19 with prephitmp.26_37 in D.1637_20 = *D.1636_19; The above is the perfect, expected, PRE result for this testcase. The real difference in assembly here is because in motion result duplicates the actual addition, and we just leave it as the result of a phi merge of the two variables. IE motion_results produces j = blah1 + blah2 in both the if and else block, and merge the j result motion_test2 keeps one copy of j = blah1 + blah2 in the main code path, and merges the blah1 and blah2 results The second is smaller, and no more or less efficient since the addition is calculated on both paths anyway. Both are valid results, and what RTL does with them is it's business. I don't believe you can claim they should generate identical assembly. The actual thing this testcase is trying to test, that load-PRE is performed, has succeeded. Thus i am closing this bug as WORKSFORME. If you see something *actually wrong* with the result, rather than just disassembly, please feel free to reopen. -- dberlin at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30105
[Bug tree-optimization/30105] reassoc can sometimes get in the way of PRE
--- Comment #4 from dberlin at gcc dot gnu dot org 2006-12-09 14:40 --- Uh, before declaring it a reassociation issue, why don't you try turning off reassoc and see if it actually fixes the problem. As long as reassoc rewrites it the same everywhere, it would still be PRE'd. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30105
[Bug tree-optimization/30103] missed strength reduction optimization (test replacement)
--- Comment #3 from rguenth at gcc dot gnu dot org 2006-12-09 14:34 ---
Uh, indeed the testcase is invalid. Using unsigned int or -fwrapv instead
makes it valid. But we still have
strength_test10 (data)
{
unsigned int ivtmp.31;
int * pretmp.23;
int stop;
:
stop = *(data + 12B);
pretmp.23 = data + 8B;
ivtmp.31 = 0;
:;
*((int *) ((unsigned int) *pretmp.23 * 4) + data) = (int) ivtmp.31;
ivtmp.31 = ivtmp.31 + 21;
if (stop > (int) (ivtmp.31 * 1022611261)) goto ; else goto ;
:;
return;
}
so we don't fix up the exit test, also with unsigned.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
CC||rakdver at gcc dot gnu dot
||org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30103
[Bug c/19977] overflow in non-static initializer should not be pedwarn
--- Comment #2 from manu at gcc dot gnu dot org 2006-12-09 14:28 --- I believe that the culprit is a call to constant_expression_warning at c-typeck.c (store_init_value). The comment just above this call says "ANSI wants warnings about out-of-range constant initializers". However, if the out-of-range constant initialiser is the result of an operation, a warning has been emitted already by overflow_warning. If the out-of-range is the result of a value that overflowed when converted to the type of the variable, a warning should have been emitted by convert_and_check. So my question is, are we required to emit a special (pedantic) warning for: int c= INT_MAX + 1; different from the warning we already give for: int c; c = INT_MAX + 1; ? -- manu at gcc dot gnu dot org changed: What|Removed |Added CC||manu at gcc dot gnu dot org Last reconfirmed|2005-12-18 01:39:36 |2006-12-09 14:28:13 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19977
[Bug tree-optimization/30103] missed strength reduction optimization (test replacement)
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-09 14:26 --- Actually we do the strength reduction for t but don't fix it up so we multiply stop by 21 but instead we add a multiply for the IV to convert back to the "normal" t. I wonder if this is because of overflow reasons and which case this testcase inside the benchmark is invalid. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30103
[Bug middle-end/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-12-09 14:24 ---
After gimplification:
D.1853 = *t;
if (D.1853 == __complex__ (0.0, 0.0))
{
D.1854 = __complex__ (0.0, 0.0);
iftmp.0 = &D.1854;
}
else
{
D.1855 = *t;
D.1856 = -D.1855;
iftmp.0 = &D.1856;
}
D.1857 = REALPART_EXPR <*iftmp.0>;
*b = D.1857;
Before:
*b = REALPART_EXPR <*t == __complex__ (0.0, 0.0) ? __complex__ (0.0, 0.0) :
-*t>;
I have not figured out why we need to take the address of the temp variable
yet.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug middle-end/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-09 14:22 --- Also note moving catching it earlier makes this a middle-end (gimplifier) issue rather than an optimization issue. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Component|tree-optimization |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug tree-optimization/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-09 14:20 --- Note, what we have is invalid gimple which we don't catch until tree-complex.c which is wrong, I have a patch to catch it earlier. Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 14:20:41 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with 4.2.0 ada
--- Comment #7 from charlet at adacore dot com 2006-12-09 13:55 --- Subject: Re: Cannot bootstrap 4.1.2 ada with 4.2.0 ada > I see it's not "supported", but as Ada needs Ada to be bootstrapped how do you > expect maintainance work to work for active release branches? By simply using an older bootstrap compiler, for both 4.1 and 4.2 Arno -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug tree-optimization/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-09 13:20 --- The gimplifier is messing up ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug tree-optimization/30132] [4.1/4.2/4.3 Regression] ICE in find_lattice_value, at tree-complex.c:133
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Keywords||ice-on-valid-code Known to fail||4.1.2 4.2.0 4.3.0 Known to work||4.0.4 Summary|ICE in find_lattice_value, |[4.1/4.2/4.3 Regression] ICE |at tree-complex.c:133 |in find_lattice_value, at ||tree-complex.c:133 Target Milestone|--- |4.1.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug c/30133] getc in printf (similar nonbug increment/decrement)
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-09 13:13 --- Order of evaulation inside function agruments is not specified by the C standard as the comma inside the function arguments is not a sequence point. So the order of the calls to getc could be any order. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30133
[Bug boehm-gc/21942] boehm-gc doesn't compile on Solaris 10/amd64
--- Comment #5 from ebotcazou at gcc dot gnu dot org 2006-12-09 12:57 --- Rainer, I'm interested in helping to port boehm-gc/libgcj to AMD64/Solaris 10, including investigating the switch to POSIX threads on all architectures. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21942
[Bug c/30133] New: getc in printf (similar nonbug increment/decrement)
$gcc -v
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.11/3.4.3/specs
Configured with: /builds1/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as
--with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++,f77
--enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-20050802)
#include
int
main(void)
{
FILE *fr = fopen("text.txt","r"); /* ABCDEFGH */
/* prints HGFEDCBA
* with cc works well
*/
printf("%c%c%c%c%c%c%c%c\n",
getc(fr), getc(fr), getc(fr), getc(fr), getc(fr), getc(fr),
getc(fr), getc(fr));
return 0;
}
--
Summary: getc in printf (similar nonbug increment/decrement)
Product: gcc
Version: 3.4.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dosout1 at fel dot cvut dot cz
GCC host triplet: any
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30133
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with 4.2.0 ada
--- Comment #6 from rguenth at gcc dot gnu dot org 2006-12-09 12:15 --- So, I'll just not include Ada in the enabled languages for bootstrapping and regtesting patches for the 4.1 branch. (As a natural consequence...) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug fortran/29941] gfortran reports error with len of assumed size character array
--- Comment #3 from patchapp at dberlin dot org 2006-12-09 12:15 --- Subject: Bug number PR29941 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/2006-12/msg00609.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29941
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with 4.2.0 ada
--- Comment #5 from rguenth at gcc dot gnu dot org 2006-12-09 12:13 --- I see it's not "supported", but as Ada needs Ada to be bootstrapped how do you expect maintainance work to work for active release branches? Given PR29127 and PR864 it's not easily possible to switch to an alternate host compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with 4.2.0 ada
--- Comment #4 from rguenth at gcc dot gnu dot org 2006-12-09 12:11 --- Err, with 4.2.0 ada actually. I wonder if we can make the stage1 ada flags more permissive somehow? -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Keywords||build Summary|Cannot bootstrap 4.1.2 ada |Cannot bootstrap 4.1.2 ada |with mainline |with 4.2.0 ada http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with mainline
--- Comment #3 from charlet at gcc dot gnu dot org 2006-12-09 12:03 --- This is not something which is supported nor guaranteed to work. You would need to do all kinds of changes in the 4.1 branch to get this work, and continue patching as the trunk compiler evolves. That being said, the changes are usually fairly mechanical: For erroutc.adb, this is trivial to fix (remove the with clause). For s-wchcon.ads, you will need to add a pragma Elaborate_Body in s-wchconv.adb and provide an empty body. Feel free to submit patches of this kind for the 4.1 branch if that's bothering for you. Arno -- charlet at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug c++/30129] [4.1 regression] ICE (segfault) in C++ code
--- Comment #3 from doko at ubuntu dot com 2006-12-09 11:39 --- works in Debian unstable as well; Ubuntu specific. -- doko at ubuntu dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30129
[Bug tree-optimization/30132] ICE in find_lattice_value, at tree-complex.c:133
--- Comment #1 from debian-gcc at lists dot debian dot org 2006-12-09
11:33 ---
Created an attachment (id=12774)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12774&action=view)
preprocessed source
#include
void testit(double complex* t, double* b)
{
b[0] = t[0]==0.0?0.0:-t[0];
}
main(void)
{
static double complex k = 5;
static double b;
testit(&k,&b);
}
The following modification fixes the problem:
void testit(double complex* t, double* b)
{
b[0] = t[0]==0.0?0.0:__real__(-t[0]);
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug tree-optimization/30132] New: ICE in find_lattice_value, at tree-complex.c:133
[forwarded from http://bugs.debian.org/400484] seen on i486-linux-gnu with 3.4, 4.1.2, 4.3 20061022, works with -O0 $ gcc -c -O1 complex.c complex.c: In function 'testit': complex.c:4: internal compiler error: in find_lattice_value, at tree-complex.c:133 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE in find_lattice_value, at tree-complex.c:133 Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30132
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with mainline
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-12-09 11:18 --- (no idea how to fix the issue in comment #2) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug ada/30130] Cannot bootstrap 4.1.2 ada with mainline
--- Comment #1 from rguenth at gcc dot gnu dot org 2006-12-09 11:12 --- Continues with gcc -c -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -gnatpg -gnata -I- -I. -Iada -I../../gcc/ada ../../gcc/ada/s-wchcon.ads -o ada/s-wchcon.o s-wchcon.ads:41:15: package "System.Wch_Con" does not allow a body s-wchcon.ads:41:15: remove incorrect body in file "s-wchcon.adb" make[2]: *** [ada/s-wchcon.o] Error 1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug target/30131] ICE in propagate_one_insn, at flow.c:1583
--- Comment #1 from debian-gcc at lists dot debian dot org 2006-12-09 11:12 --- Created an attachment (id=12773) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12773&action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30131
[Bug target/30131] New: ICE in propagate_one_insn, at flow.c:1583
[forwarded from http://bugs.debian.org/397341] seen with 3.4, 4.1, 4.3 SVN 20061022 on hppa-linux-gnu with -O1, -O2, works with -O0. $ gcc -c -g -O2 pdvitomp.i pdvitomp.c: In function `parsearguments': pdvitomp.c:174: error: Attempt to delete prologue/epilogue insn: (insn/f 1017 1016 1018 0 pdvitomp.c:99 (set (mem:SI (plus:SI (reg/f:SI 30 %r30) (const_int -124 [0xff84])) [0 S4 A32]) (reg:SI 13 %r13)) -1 (nil) (nil)) pdvitomp.c:174: internal compiler error: in propagate_one_insn, at flow.c:1583 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE in propagate_one_insn, at flow.c:1583 Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org GCC target triplet: hppa-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30131
[Bug c++/30129] [4.1 regression] ICE (segfault) in C++ code
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-12-09 11:11 --- works with 4.1.2 r119687. Works with g++ (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux). g++-4.1 -v? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30129
[Bug target/30128] Strange code generated
--- Comment #1 from rguenth at gcc dot gnu dot org 2006-12-09 11:02 --- This is because for the first line (*((char *)(p) + 0) = (char) ((dat)) & 0xff) we do the len + 1 in unsigned char type (we recognize x & 0xff as a cast to unsigned char). So we have two additions and cannot figure out in the end that one is redundant. (we might have a dup for this) -- rguenth at gcc dot gnu dot org changed: What|Removed |Added CC||rguenth at gcc dot gnu dot ||org Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 GCC build triplet|i586-suse-linux | GCC host triplet|i586-suse-linux | GCC target triplet|i586-suse-linux | Keywords||missed-optimization Last reconfirmed|-00-00 00:00:00 |2006-12-09 11:02:10 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30128
[Bug fortran/30115] allocate() interface pessimizes aliasing
--- Comment #7 from rguenth at gcc dot gnu dot org 2006-12-09 10:23 --- I guess it may work to only change void allocate (void **, size_t, int *) to void *allocate (void *, size_t, int *) and use it like descriptor.data = allocate (descriptor.data, size, pstat) the point is that aliasing needs a SSA_NAME def for the newly allocated memory to assign it a unique alias set. With the current interface we get only a clobber of the descriptor.data (a VDEF) from which we cannot do any alias set modification. I believe this interface change could work without violating any parts of the standard (as it really doesn't change semantics)? (confirming this, the middle-end is really pessimized by the current interface) -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 10:23:27 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30115
[Bug c++/30129] [4.1 regression] ICE (segfault) in C++ code
--- Comment #1 from doko at ubuntu dot com 2006-12-09 10:20 --- works with 4.0.3 -- doko at ubuntu dot com changed: What|Removed |Added Known to work||4.0.3 Summary|ICE (segfault) in C++ code |[4.1 regression] ICE ||(segfault) in C++ code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30129
[Bug ada/30130] New: Cannot bootstrap 4.1.2 ada with mainline
because gcc -c -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -gnatpg -gnata -I- -I. -Iada -I../../gcc/ada ../../gcc/ada/erroutc.adb -o ada/erroutc.o erroutc.adb:42:06: warning: redundant with clause in body make[2]: *** [ada/erroutc.o] Error 1 -- Summary: Cannot bootstrap 4.1.2 ada with mainline Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rguenth at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30130
[Bug fortran/30096] Interface bug: gfortran falsely detect ambigious interface, scoping problem?
--- Comment #5 from patchapp at dberlin dot org 2006-12-09 10:01 --- Subject: Bug number PR30096 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/2006-12/msg00605.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30096
[Bug c++/30129] New: ICE (segfault) in C++ code
[forwarded from http://launchpad.net/bugs/74248] ICE building kdelibs4 on amd64; i386 works ok. seen with 4.1.2 20061208. $ g++-4.1 -c -o test.o bug.ii /home/simon/src/kde/kdelibs/phonon/objectdescription.cpp: In member function Phonon::ObjectDescription& Phonon::ObjectDescription::operator=(const Phonon::ObjectDescription&): /home/simon/src/kde/kdelibs/phonon/objectdescription.cpp:54: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE (segfault) in C++ code Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: doko at ubuntu dot com GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30129
[Bug boehm-gc/21942] boehm-gc doesn't compile on Solaris 10/amd64
--- Comment #4 from ebotcazou at gcc dot gnu dot org 2006-12-09 08:21 --- In case someone is still doubtful. :-) -- ebotcazou at gcc dot gnu dot org changed: What|Removed |Added CC||ebotcazou at gcc dot gnu dot ||org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-12-09 08:21:06 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21942
