Re: [Bug fortran/57364] [4.8/4.9 Regression][OOP] ICE gfc_enforce_clean_symbol_state
Le 22/05/2013 11:22, burnus at gcc dot gnu.org a écrit : --- a/gcc/fortran/resolve.c +++ b/gcc/fortran/resolve.c @@ -9299,4 +9299,5 @@ get_temp_from_expr (gfc_expr *e, gfc_namespace *ns) tmp-n.sym-attr.dimension = 0; + gfc_commit_symbol (tmp-n.sym); gfc_set_sym_referenced (tmp-n.sym); gfc_add_flavor (tmp-n.sym-attr, FL_VARIABLE, name, NULL); Without looking at the code, gfc_commit_symbol should come after the gfc_set_sym_referenced, gfc_add_flavor, etc, and any modification made to tmp-n.sym.
Re: version `GLIBC_2.14' not found (required by build/genhooks)
On Thursday 22 September 2011 11:56:12 Teodori Serge wrote: Hello, I'm building a toolchain in /opt dir. I have already build and installed glibc-2.14 and binutils-2.21.1a in /opt. Now I want to build and install gcc-4.6.1 with gmp, mpfr and mpc also in /opt. Here is my configure: ../gcc-4.6.1/configure --prefix=/tools --disable-nls --disable-shared --disable-multilib --disable-decimal-float --disable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libquadmath --disable-target-libiberty --disable-target-zlib --enable-languages=c --without-ppl --without-cloog Here is the last output of my build: build/genhooks tmp-target-hooks-def.h build/genhooks: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by build/genhooks) make[3]: *** [s-target-hooks-def-h] Error 1 make[3]: *** Waiting for unfinished jobs rm gcc.pod make[3]: Leaving directory `/home/serge/Documents/gcc-build/gcc' make[2]: *** [all-stage2-gcc] Error 2 make[2]: Leaving directory `/home/serge/Documents/gcc-build' make[1]: *** [stage2-bubble] Error 2 make[1]: Leaving directory `/home/serge/Documents/gcc-build' make: *** [all] Error 2 The problem is very obvious, gcc build is not taking the toolchain glibc-2.14 in /opt/lib but it is taking the one the host uses which is eglibc-2.13 in /usr/lib. I set various flags to the linker and compiler, they are all looking in the right directory. It must be something in the configure script? Can anyone help me please. Thank you It seems the generated program genhooks is correctly linked to your new glibc. However, you need to either set LD_LIBRARY_PATH or change the /etc/ld.so.conf configuration file so that genhooks loads the right library when it is executed. Mikael. PS: this list is for the automatic messages generated by the bug tracking system at http://gcc.gnu.org/bugzilla. For questions, you should use the gcc-help mailing list.
Re: [Bug libfortran/46182] New: Run time check for invalid use of unallocated allocatable variables
It would be nice to have a run time check for such invalid use of unallocated allocatable variables (such as -fcheck=use_unalloc). If you use an unallocated variable you get a segmentation fault. Isn't this a sufficient runtime check ?
Re: [Bug fortran/40054] [F08] Pointer functions as lvalue
two() = 7 I don't see how it is possible to distinguish between a statement function and an assignment here.
Re: [Bug fortran/41359] Wrong line numbers for debugging/profiling
this still fails with a recent trunk. Mikael, do you plan to commit your patch? Thanks for the remainder. I'm currently on something else, but I plan to do it during stage 3.
Re: [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects
On Friday 01 October 2010 16:39:35 jvdelisle at gcc dot gnu.org wrote: 2010-10-01 14:39:23 UTC --- This look suspicious: valgrind on f951 No, it is unrelated. It happens on the most simple testcases like: end It can be circumvented by the following patch. But it is harmless (unreleased memory). --- a/cpp.c +++ b/cpp.c @@ -510,10 +510,11 @@ gfc_cpp_post_options (void) || gfc_cpp_option.dump_includes)) gfc_fatal_error(To enable preprocessing, use -cpp); - cpp_in = cpp_create_reader (CLK_GNUC89, NULL, line_table); if (!gfc_cpp_enabled ()) return; + cpp_in = cpp_create_reader (CLK_GNUC89, NULL, line_table); + gcc_assert (cpp_in); /* The cpp_options-structure defines far more flags than those set here.
