[Bug fortran/28484] F2003: system_clock with real-type count_rate does not compile
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-04-11 21:35 --- Raising this up a little since F2003 features are coming up -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Severity|enhancement |normal Summary|system_clock with real-type |F2003: system_clock with |count_rate does not compile |real-type count_rate does ||not compile http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28484
[Bug target/39740] unrecognizable insn on alpha using -O3 and -std=c99
--- Comment #5 from kurt at roeckx dot be 2009-04-11 21:30 --- It's building now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug target/39738] GCC cannot build itself for win64 platform
--- Comment #3 from css20 at mail dot ru 2009-04-11 21:09 --- > Are you sure your entire compiler is up to date, not just the library? No.. it was not lasest snapshot (20090331). > We solve this by setting up in gcc's source tree a symbolic link "winsup" > pointing to the sysroot (prefix) directory I move to gcc-4.4.0-20090407, create symbolik link to my prefix directory (/usr/win64), but build not successfully.. make running from build/x86_64-pc-mingw32/libstdc++-v3/src: /bin/sh ../libtool --tag CXX --mode=compile x86_64-pc-mingw32-c++ -L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/mingw -L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/w32api/lib -isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/mingw/include -isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/w32api/include -I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/x86_64-pc-mingw32 -I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include -I/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2 -std=gnu++0x -c ../../../../src/libstdc++-v3/src/atomic.cc libtool: compile: x86_64-pc-mingw32-c++ -L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/mingw -L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/w32api/lib -isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/mingw/include -isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/w32api/include -I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/x86_64-pc-mingw32 -I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include -I/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2 -std=gnu++0x -c ../../../../src/libstdc++-v3/src/atomic.cc -o atomic.o In file included from /usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/utility:88, from /usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/tuple:43, from /usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/mutex:44, from ../../../../src/libstdc++-v3/src/atomic.cc:33: /usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++/initializer_list: In constructor 'std::initializer_list<_E>::initializer_list()': /usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++/initializer_list:59: error: 'NULL' was not declared in this scope There is a possibility of manual build.. call make with these options make -j9 CFLAGS="-g -O2 -DNULL=0" CXXFLAGS="-g -O2 -DNULL=0 and compile remaining parts of gcc from root build directory, but it is not too convenient... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
[Bug bootstrap/39704] [4.5 Regression] Revision 145841 breaks bootstrap on powerpc-apple-darwin9
--- Comment #4 from dominiq at lps dot ens dot fr 2009-04-11 20:31 --- Fixed at revision 145896. Closing. -- dominiq at lps dot ens dot fr changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39704
[Bug rtl-optimization/37377] [4.4 Regression] Bootstrap failure compiling libgcc
--- Comment #16 from tkoenig at gcc dot gnu dot org 2009-04-11 19:48 --- Subject: Bug 37377 Author: tkoenig Date: Sat Apr 11 19:48:19 2009 New Revision: 145965 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145965 Log: 2009-04-11 Thomas Koenig PR fortran/37377 * libgfortran.h: Introduce new macros GFC_DIMENSION_LBOUND, GFC_DIMENSION_UBOUND,GFC_DIMENSION_STRIDE, GFC_DIMENSION_EXTENT, GFC_DIMENSION_SET, GFC_DESCRIPTOR_LBOUND, GFC_DESCRIPTOR_UBOUND, GFC_DESCRIPTOR_EXTENT, GFC_DESCRIPTOR_EXTENT_BYTES, GFC_DESCRIPTOR_STRIDE, GFC_DESCRIPTOR_STRIDE_BYTES * runtime/in_pack_generic.c (internal_pack): Use new macros for array descriptor access. * runtime/in_unpack_generic.c (internal_unpack): Likewise. * intrinsics/dtime.c (dtime_sub): Likewise. * intrinsics/cshift0 (cshift0): Remove argument size, calculate directly from the array descriptor. Use new macros for array descriptor access. * cshift0_##N: Remove shift argument in call to cshift0. * cshift0_##N_char: Mark array_length as unused. Remove array_length in call to cshift0. * cshift0_##N_char4: Likewise. * intrisics/etime.c: Use new macros for array descriptor access. * intrinsics/stat.c (stat_i4_sub_0): Likewise. (stat_i8_sub_0): Likewise. (fstat_i4_sub): Likewise. (fstat_i8_sub): Likewise. * intrinsics/date_and_time.c (date_and_time): Likewise. (secnds): Likewise. (itime_i4): Likewise. (itime_i8): Likewise. (idate_i4): Likewise. (idate_i8): Likewise. (gmtime_i4): Likewise. (gmtime_i8): Likewise. (ltime_i4): Likewise. (litme_i8): Likewise. * intrinsics/associated.c (associated): Likewise. * intrinsics/eoshift0.c (eoshift0): Likewise. * intriniscs/size.c (size0): Likewise. * intrinsics/random.c (arandom_r4): Likewise. (arandom_r8): Likewise. (arandom_r10): Likewise. (arandom_r16): Likewise. (random_seed_i4): Likewise. (random_seed_i8): Likewise. * io/list_read.c (nml_parse_qualifier): Likewise. (nml_touch_nodes): Likewise. (nml_read_obj): Likewise. (get_name): Likewise. * io/transfer.c (transfer_array): Likewise. (init_loop_spec): Likewise. (st_set_nml_var_dim): Likewise. * io/write.c (nml_write_obj): Likewise. (obj_loop): Likewise. Modified: branches/fortran-dev/libgfortran/ChangeLog.dev branches/fortran-dev/libgfortran/intrinsics/associated.c branches/fortran-dev/libgfortran/intrinsics/cshift0.c branches/fortran-dev/libgfortran/intrinsics/date_and_time.c branches/fortran-dev/libgfortran/intrinsics/dtime.c branches/fortran-dev/libgfortran/intrinsics/eoshift0.c branches/fortran-dev/libgfortran/intrinsics/etime.c branches/fortran-dev/libgfortran/intrinsics/random.c branches/fortran-dev/libgfortran/intrinsics/size.c branches/fortran-dev/libgfortran/intrinsics/stat.c branches/fortran-dev/libgfortran/io/list_read.c branches/fortran-dev/libgfortran/io/transfer.c branches/fortran-dev/libgfortran/io/write.c branches/fortran-dev/libgfortran/libgfortran.h branches/fortran-dev/libgfortran/runtime/in_pack_generic.c branches/fortran-dev/libgfortran/runtime/in_unpack_generic.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37377
[Bug target/39740] unrecognizable insn on alpha using -O3 and -std=c99
--- Comment #4 from ubizjak at gmail dot com 2009-04-11 19:47 --- Kurt, can you perhaps bootstrap and regression test attached patch? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug target/39740] unrecognizable insn on alpha using -O3 and -std=c99
--- Comment #3 from ubizjak at gmail dot com 2009-04-11 19:46 --- Created an attachment (id=17622) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17622&action=view) patch This patch declares (const:DI (plus:DI (label_ref:DI 74) (const_int 24 [0x18]))) as local_symbolic_operand and fixes the failure. -- ubizjak at gmail dot com changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |ubizjak at gmail dot com |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug target/39740] unrecognizable insn on alpha using -O3 and -std=c99
--- Comment #2 from ubizjak at gmail dot com 2009-04-11 19:40 --- Confirmed with x86_64 cross on 4.3 and 4.4. -- ubizjak at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2009-04-11 19:40:00 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug target/39738] GCC cannot build itself for win64 platform
--- Comment #2 from ktietz at gcc dot gnu dot org 2009-04-11 19:33 --- (In reply to comment #1) > Are you sure your entire compiler is up to date, not just the library? And the > build and install directories are clean? Because your first lines of failure > involve bits of the library which *require* a consistent simultaneous change > in > the C++ front-end, and well, nobody is experiencing similar problems anywhere. > Not that this code is target-independent. > > CC-ing Jason, the author of such code, to be sure. > Well, on 4.4 branch there was a patch introducing the winsup link, which got necessary for building libstdc++. We solve this by setting up in gcc's source tree a symbolic link "winsup" pointing to the sysroot (prefix) directory. Cheers, Kai -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
[Bug libstdc++/39738] GCC cannot build itself for win64 platform
--- Comment #1 from paolo dot carlini at oracle dot com 2009-04-11 18:47 --- Are you sure your entire compiler is up to date, not just the library? And the build and install directories are clean? Because your first lines of failure involve bits of the library which *require* a consistent simultaneous change in the C++ front-end, and well, nobody is experiencing similar problems anywhere. Not that this code is target-independent. CC-ing Jason, the author of such code, to be sure. -- paolo dot carlini at oracle dot com changed: What|Removed |Added CC||jason at gcc dot gnu dot org Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|blocker |normal http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #8 from ktietz at gcc dot gnu dot org 2009-04-11 17:33 --- (In reply to comment #5) > stdio.h at system level is where it originally was: > > /usr/include/stdio.h > /usr/include/c++/4.2.1/tr1/stdio.h > /usr/include/bits/stdio.h Ok, this is what I assumed. You are building a mingw cross-compiler on a linux host. So the headers from linux aren't usable for the cross-compiler. For such a scenario, normally /usr/local is the default sysroot. You can take a look on http://sourceforge.net/docman/?group_id=202880 in the document "mingw-w64-howto-build". We describe here the build of x64 version of mingw, but by replacing x86_64-pc-mingw32 by i686-pc-mingw32 it should work for you. Also you can use the user mailing list on mingw.org for such issues. Cheers, Kai -- ktietz at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug target/39740] unrecognizable insn on alpha using -O3 and -std=c99
--- Comment #1 from kurt at roeckx dot be 2009-04-11 17:23 --- Created an attachment (id=17621) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17621&action=view) Reduced test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug target/39740] New: unrecognizable insn on alpha using -O3 and -std=c99
Hi, r-base is failing to build on alpha with the following error: gcc -I. -I../../src/include -I../../src/include -DHAVE_CONFIG_H -mieee-with-inexact -fpic -std=gnu99 -O3 -pipe -g -c deriv.c -o deriv.o deriv.c: In function 'simplify': deriv.c:267: error: unrecognizable insn: (insn 2103 64 65 9 ../../src/include/Rinlinedfuns.h:86 (set (reg:DI 2 $2) (const:DI (plus:DI (label_ref:DI 68) (const_int 24 [0x18] -1 (insn_list:REG_LABEL_OPERAND 68 (nil))) deriv.c:267: internal compiler error: in extract_insn, at recog.c:2001 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. make[4]: *** [deriv.o] Error 1 I'll attached a reduced test case that gives a simular error message: $ gcc-4.3 -std=c99 -O3 -c deriv.i -o deriv.o deriv.i: In function 'D': deriv.i:117: error: unrecognizable insn: (insn 383 189 190 26 deriv.i:42 (set (reg:DI 2 $2) (const:DI (plus:DI (label_ref:DI 193) (const_int 24 [0x18] -1 (insn_list:REG_LABEL_OPERAND 193 (nil))) deriv.i:117: internal compiler error: in extract_insn, at recog.c:2001 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. Note that the error goes away if you do not use -std=gnu99 or -std=c99, and -O3. It compiles with gcc-4.1 and 4.2. -- Summary: unrecognizable insn on alpha using -O3 and -std=c99 Product: gcc Version: 4.3.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kurt at roeckx dot be GCC host triplet: alpha-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39740
[Bug c++/35652] [4.3 Regression] offset warning should be given in the front-end
--- Comment #27 from rob1weld at aol dot com 2009-04-11 17:01 --- Ping: gcc version 4.5.0 20090407 trunk revision 145649 gcc_trunk/libiberty/cplus-dem.c:2651: warning: offset 3 outside bounds of constant string Noticed while building binutils (with -Werror): ../binutils-2.19.1/bfd/elf.c: In function '_bfd_elf_print_private_bfd_data': ../binutils-2.19.1/bfd/elf.c:1236: error: offset '2' outside bounds of constant string Thanks, Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35652
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #7 from sergstesh at yahoo dot com 2009-04-11 17:01 --- Regarding "Could you attach the build log?" - isn't it already attached http://gcc.gnu.org/bugzilla/attachment.cgi?id=17620 ? The file is gzipped because in plain form it's bigger than 1MB. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #6 from sergstesh at yahoo dot com 2009-04-11 16:55 --- Sorry, not "Also, there were 'binutils' elements in the paths." , but Also, there were no 'binutils' elements in the paths. . -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #5 from sergstesh at yahoo dot com 2009-04-11 16:54 --- stdio.h at system level is where it originally was: /usr/include/stdio.h /usr/include/c++/4.2.1/tr1/stdio.h /usr/include/bits/stdio.h . Regarding 'gcc' configure options - do you mean normal native 'gcc' or the 'gcc' for cross compilation I've filed the report against ? Anyway, the answers are in the already attached http://gcc.gnu.org/bugzilla/attachment.cgi?id=17618 . Native 'gcc' was built with the same options, but without --target=i686-pc-mingw32, i.e. '--target' was not at all specified on command line. Also, there were 'binutils' elements in the paths. Do you also need 'config.log' ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug fortran/37746] bounds check of string dummy arguments
--- Comment #8 from domob at gcc dot gnu dot org 2009-04-11 16:46 --- Fixed on trunk. -- domob at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37746
[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor
--- Comment #31 from jvdelisle at gcc dot gnu dot org 2009-04-11 16:45 --- now that 4.5 branch is alive I will try once again to submit patch for approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784
[Bug fortran/37746] bounds check of string dummy arguments
--- Comment #7 from domob at gcc dot gnu dot org 2009-04-11 16:44 --- Subject: Bug 37746 Author: domob Date: Sat Apr 11 16:44:37 2009 New Revision: 145958 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145958 Log: 2009-04-11 Daniel Kraft PR fortran/37746 * gfortran.h (struct gfc_charlen): New field `passed_length' to store the actual passed string length for dummy arguments. * trans-decl.c (gfc_create_string_length): Formatting fixes and added assertion, moved a local variable into the innermost block it is needed. (create_function_arglist): Removed TODO about the check being implemented and initialize cl->passed_length here. (add_argument_checking): New method. (gfc_generate_function_code): Call the argument checking method. 2009-04-11 Daniel Kraft PR fortran/37746 * gfortran.dg/bounds_check_strlen_1.f90: New test. * gfortran.dg/bounds_check_strlen_2.f90: New test. * gfortran.dg/bounds_check_strlen_3.f90: New test. * gfortran.dg/bounds_check_strlen_4.f90: New test. * gfortran.dg/bounds_check_strlen_5.f90: New test. * gfortran.dg/bounds_check_strlen_6.f90: New test. * gfortran.dg/bounds_check_strlen_7.f90: New test. * gfortran.fortran-torture/execute/intrinsic_index.f90: Fix wrong expected string length that failed with -fbounds-check now. * gfortran.fortran-torture/execute/intrinsic_trim.f90: Ditto. Added: trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_1.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_2.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_3.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_4.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_5.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_6.f90 trunk/gcc/testsuite/gfortran.dg/bounds_check_strlen_7.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.fortran-torture/execute/intrinsic_index.f90 trunk/gcc/testsuite/gfortran.fortran-torture/execute/intrinsic_trim.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37746
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #4 from ktietz at gcc dot gnu dot org 2009-04-11 16:36 --- Where are your headers installed? To which directory? And of interest is the configure options you are passing to gcc's configure, too. Could you attach the build log? Kai -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug c/35634] [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement not promoted
--- Comment #24 from rguenther at suse dot de 2009-04-11 16:32 ---
Subject: Re: [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement
not promoted
On Sat, 11 Apr 2009, joseph at codesourcery dot com wrote:
> --- Comment #23 from joseph at codesourcery dot com 2009-04-11 16:30
> ---
> Subject: Re: [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement
> not promoted
>
> On Sat, 11 Apr 2009, rguenth at gcc dot gnu dot org wrote:
>
> > On no-undefined-overflow branch the FE can do the increment/decrement on the
> > target type safely (well, there are no NV variants of the
> > {PRE,POST}{IN,DEC}REMENT
> > expressions on the branch, so they at the moment all get lowered to
> > possibly wrapping variants during gimplification).
>
> Of course increment/decrement of signed integer types at least as wide as
> int should get lowered to the no-overflow variants unless -fwrapv;
> likewise increment/decrement of pointer types. Whether through a
> gimplification-time hook or through creating NV variants of
> increment/decrement and having the front end create those when
> appropriate.
Indeed. As they are not valid gimple but only in generic I lean
to a gimplification-time solution here.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35634
[Bug c/35634] [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement not promoted
--- Comment #23 from joseph at codesourcery dot com 2009-04-11 16:30
---
Subject: Re: [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement
not promoted
On Sat, 11 Apr 2009, rguenth at gcc dot gnu dot org wrote:
> On no-undefined-overflow branch the FE can do the increment/decrement on the
> target type safely (well, there are no NV variants of the
> {PRE,POST}{IN,DEC}REMENT
> expressions on the branch, so they at the moment all get lowered to
> possibly wrapping variants during gimplification).
Of course increment/decrement of signed integer types at least as wide as
int should get lowered to the no-overflow variants unless -fwrapv;
likewise increment/decrement of pointer types. Whether through a
gimplification-time hook or through creating NV variants of
increment/decrement and having the front end create those when
appropriate.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35634
[Bug libfortran/39668] Wrongly read namelist with two dimensional array.
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-04-11 16:28 --- Un-assigning, I don't think this is a bug, yet. :) -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|jvdelisle at gcc dot gnu dot|unassigned at gcc dot gnu |org |dot org Status|WAITING |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39668
[Bug fortran/22552] Would like warning when an undeclared function is called
--- Comment #4 from domob at gcc dot gnu dot org 2009-04-11 16:14 --- Extended patch based on the one from comment #2 posted: http://gcc.gnu.org/ml/fortran/2009-04/msg00148.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22552
[Bug c/35634] [4.3/4.4/4.5 Regression] operand of pre-/postin-/decrement not promoted
--- Comment #22 from rguenth at gcc dot gnu dot org 2009-04-11 15:58
---
On no-undefined-overflow branch the FE can do the increment/decrement on the
target type safely (well, there are no NV variants of the
{PRE,POST}{IN,DEC}REMENT
expressions on the branch, so they at the moment all get lowered to
possibly wrapping variants during gimplification).
Unfortunately that branch is way from "ready".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35634
[Bug middle-end/30447] Evaluate complex math functions at compile-time
--- Comment #7 from ghazi at gcc dot gnu dot org 2009-04-11 15:55 --- Patches to integrate the MPC library posted here: http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00671.html http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00672.html http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00673.html http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00674.html http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00675.html They require some updating for current mainline. MPC version 0.6 has been reported to work on all of GCC's primary and secondary platforms, as well as many others: http://www.multiprecision.org/index.php?prog=mpc&page=platforms -- ghazi at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2007-01-12 16:38:37 |2009-04-11 15:55:05 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30447
[Bug fortran/39587] Reading integer from "" gives end-of-file instead of reading a 0
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-04-11 15:46 --- I think gfortran has this right. This is an attempt to read from an internal unit of length zero. Try the same operation from a zero length file. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39587
[Bug bootstrap/39739] Bootstrapping with in-tree mpfr-2.4.1 and --with-gmp=... errors
-- ghazi at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.3.4 Version|4.3.4 |4.3.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39739
[Bug bootstrap/39739] Bootstrapping with in-tree mpfr-2.4.1 and --with-gmp=... errors
-- ghazi at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |ghazi at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2009-04-11 15:37:37 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39739
[Bug bootstrap/39739] New: Bootstrapping with in-tree mpfr-2.4.1 and --with-gmp=... errors
Bootstrapping with an in-tree copy of mpfr (version 2.4.1) and using an installed gmp in a directory specified by --with-gmp=foo yields an error when the bootstrap process gets to configuring the mpfr dir: > configure: error: Do not use --with-gmp-build and other --with-gmp options simultaneously. > See `config.log' for more details. > make[1]: *** [configure-mpfr] Error 1 Older versions of mpfr built in-tree are more forgiving and mask the issue but the bug is merely latent in those cases. The problem is that the top-level configure process assumes that if one is building mpfr in-tree then gmp is also being built in-tree and therefore the second --with-gmp* flag is specified pointing to the a gmp build dir which does not exist in this scenario. More details are found here: http://gcc.gnu.org/ml/gcc/2009-04/msg00342.html http://gcc.gnu.org/ml/gcc/2009-04/msg00364.html The solution is to only pass --with-gmp-build= when one is actually building gmp in-tree regardless of what's going on with mpfr. -- Summary: Bootstrapping with in-tree mpfr-2.4.1 and --with-gmp=... errors Product: gcc Version: 4.3.4 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ghazi at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39739
[Bug fortran/25829] [F2003] Asynchronous IO support
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-04-11 15:26 --- gfortran currently accepts asynchronous I/O syntax. The F2003 standard permits the implementation to actually do synchronous I/O. gfortran run time library does not actually perform I/O asynchronously, but does so synchronously. To implement this we need to develop the underlying scheme with the unit and DTP structures, develop config magic to identify targets that actually have support for asynchronous I/O, write the code that keeps track of the I/O calls, there status and completion, and address the threading concerns. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829
[Bug libstdc++/39738] New: GCC cannot build itself for win64 platform
build log from x86_64-pc-mingw32/libstdc++-v3/include: mkdir -p ./x86_64-pc-mingw32/bits/stdc++.h.gch x86_64-pc-mingw32-c++ -L/usr/portage/local/overlays/build/x86_64-pc-mingw32/winsup/mingw -L/usr/portage/local/overlays/build/x86_64-pc-mingw32/winsup/w32api/lib -isystem /usr/portage/local/overlays/gcc-4.4.0/winsup/mingw/include -isystem /usr/portage/local/overlays/gcc-4.4.0/winsup/w32api/include -Winvalid-pch -x c++-header -g -O2 -I/usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/x86_64-pc-mingw32 -I/usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include -I/usr/portage/local/overlays/gcc-4.4.0/libstdc++-v3/libsupc++ -O2 -g -std=gnu++0x /usr/portage/local/overlays/gcc-4.4.0/libstdc++-v3/include/precompiled/stdc++.h \ -o x86_64-pc-mingw32/bits/stdc++.h.gch/O2ggnu++0x.gch In file included from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/type_traits:51, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/bits/move.h:38, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/bits/stl_pair.h:60, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/bits/stl_algobase.h:66, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/bits/char_traits.h:41, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/ios:41, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/istream:40, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/sstream:39, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/complex:47, from /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/ccomplex:42, from /usr/portage/local/overlays/gcc-4.4.0/libstdc++-v3/include/precompiled/stdc++.h:51: /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:233: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:233: error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:228: error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:236: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:236: error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ..., ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:231: error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ..., ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:239: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:239: error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:228: error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:242: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:242: error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ..., ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:231: error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ..., ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:245: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:245: error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:228: error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ...)>' /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:248: error: invalid qualifiers on non-member function type /usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:248: error: redefinition of 'struct std::is
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #3 from sergstesh at yahoo dot com 2009-04-11 14:00 --- Created an attachment (id=17620) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17620&action=view) 'make' screen output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug fortran/22552] Would like warning when an undeclared function is called
--- Comment #3 from domob at gcc dot gnu dot org 2009-04-11 13:58 --- Working on updating and working out FX's patch. -- domob at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |domob at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2007-11-08 17:59:32 |2009-04-11 13:58:04 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22552
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #2 from sergstesh at yahoo dot com 2009-04-11 13:57 --- Created an attachment (id=17619) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17619&action=view) 'configure' screen output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug bootstrap/39737] 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
--- Comment #1 from sergstesh at yahoo dot com 2009-04-11 13:55 --- Created an attachment (id=17618) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17618&action=view) autogenerated script used to run 'configure' -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug bootstrap/39737] New: 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK
I've tried to build i686-pc-mingw32 version of gcc-4.3.3 to be used as cross-compiler on Linux for Windows, and the build failed with this error message: " /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3/./gcc/xgcc -B/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3/./gcc/ -L/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3/i686-pc-mingw32/winsup/mingw -L/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3/i686-pc-mingw32/winsup/w32api/lib -isystem /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/winsup/mingw/include -isystem /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/winsup/w32api/include -B/mnt/sdb8/sergei/AFSWD_debug/install/gcc4_mingw32-4.3.3/i686-pc-mingw32/bin/ -B/mnt/sdb8/sergei/AFSWD_debug/install/gcc4_mingw32-4.3.3/i686-pc-mingw32/lib/ -isystem /mnt/sdb8/sergei/AFSWD_debug/install/gcc4_mingw32-4.3.3/i686-pc-mingw32/include -isystem /mnt/sdb8/sergei/AFSWD_debug/install/gcc4_mingw32-4.3.3/i686-pc-mingw32/sys-include -O2 -g -g -O2 -O2 -I/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/gcc/../winsup/w32api/include -O2 -g -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../.././gcc -I/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc -I/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/. -I/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/../gcc -I/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/../include -DHAVE_CC_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/../gcc/libgcc2.c \ In file included from ../.././gcc/tm.h:10, from /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/../gcc/libgcc2.c:35: /mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3.src/libgcc/../gcc/config/i386/cygming.h:68:19: error: stdio.h: No such file or directory make[2]: *** [_muldi3.o] Error 1 make[2]: Leaving directory `/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3/i686-pc-mingw32/libgcc' make[1]: *** [all-target-libgcc] Error 2 make[1]: Leaving directory `/mnt/sdb8/sergei/AFSWD_debug/build/gcc-4.3.3' make: *** [all] Error 2 " , i.e. 'stdio.h' file can't be found. Of course, the file exists in a standard location, but probably "-Dinhibit_libc" prevents 'xgcc' from seeing it. It's my first attempt to build a cross-compiler, so maybe I'm doing something wrong, anyway, I expect 'configure' to prevent me from making stupid mistakes. Self-built working quite fine native gcc-4.3.3 was used in the attempt to build the cross-compiler version. I am about to upload files with more info - command lines, screen output, etc. My OS is SUSE 10.3, 32 bits. -- Summary: 'make' for --target=i686-pc-mingw32 fails even though 'configure' is OK Product: gcc Version: 4.3.3 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sergstesh at yahoo dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39737
[Bug tree-optimization/39736] signed overflow in loop induction variable: missing warning and wrong code
--- Comment #1 from joseph at codesourcery dot com 2009-04-11 12:51 ---
Subject: Re: New: signed overflow in loop
induction variable: missing warning and wrong code
On Sat, 11 Apr 2009, edwintorok at gmail dot com wrote:
> Testcase:
> #include
> int
> main ()
> {
> int until = 40001;
> short from = 0;
>
> for (; from < until; from++)
> printf ("%d\n", from);
>
> return 0;
> }
There is no undefined behavior here (increment of a short value converts
to int, increments then converts back to short, none of which are
undefined), so at least the wrong code issue would be the same as bug
35634.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39736
[Bug tree-optimization/39736] New: signed overflow in loop induction variable: missing warning and wrong code
[This bug was discovered by kantorzs...@yahoo.com]
When compiling the testcase below at -O2, using gcc 4.3.3 instead of an infite
loop, where the variable 'from' takes values from -32768 to 32767,
it goes up way beyond that limit:
$ gcc -O2 tes -Wall -W -Wstrict-overflow=5 && ./a.out
0
1
...
2253491
When using -fwrapv, or -fno-strict-overflow 'from' iterates between -32768 and
32767 in an infinite loop, as expected.
There are 2 bugs here:
- no warning is given with -Wstrict-overflow=5, although -fstrict-overflow
changes the behaviour of the code
- from is of type short, so when sign extended to an int, it should only take
values allowed for a short: -32768 to 32767, not all values allowed for an int
(like 2253491)
I think this is a bug, because although signed overflow is undefined behaviour,
that should affect only the value of 'from', which is still of type 'short',
and converting to int should obey the limits for the 'short' type, i.e. use a
sign-extension.
Here is a diff of the assembly, when using -O2, vs -O2 -fno-strict-overflow:
--- x2.s2009-04-11 15:28:01.0 +0300
+++ x2-no-overflow.s2009-04-11 15:27:58.0 +0300
@@ -10,15 +10,16 @@
.LFB13:
pushq %rbx
.LCFI0:
+ xorl%esi, %esi
xorl%ebx, %ebx
.p2align 4,,10
.p2align 3
.L2:
- movl%ebx, %esi
movl$.LC0, %edi
xorl%eax, %eax
- callprintf
addl$1, %ebx
+ callprintf
+ movswl %bx,%esi
jmp .L2
.LFE13:
.size main, .-main
Testcase:
#include
int
main ()
{
int until = 40001;
short from = 0;
for (; from < until; from++)
printf ("%d\n", from);
return 0;
}
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --enable-mpfr --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.3 (Debian 4.3.3-5)
Also reproduced with trunk:
$ ~/gcc_inst/bin/gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc/configure --disable-multilib --disable-static
--prefix=/home/edwin/gcc_inst/ --enable-languages=c,c++
Thread model: posix
gcc version 4.5.0 20090408 (experimental) [trunk revision 145769] (GCC)
--
Summary: signed overflow in loop induction variable: missing
warning and wrong code
Product: gcc
Version: 4.3.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: edwintorok at gmail dot com
GCC build triplet: x86_64-linux-gnu
GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39736
[Bug fortran/39735] New: procedure pointer assignments: return value is not checked
Currently the validity checks for procedure pointer assignments are limited to formal/actual arguments and function/subroutine (see proc_ptr_11.f90 and PR 38290), but a check for the return value is missing. Example: procedure(real), pointer :: p1 procedure(integer), pointer :: p2 p1 => iabs p1 => p2 -- Summary: procedure pointer assignments: return value is not checked Product: gcc Version: 4.5.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: janus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39735
[Bug fortran/39692] f95: conflict between EXTERNAL and POINTER
--- Comment #3 from janus at gcc dot gnu dot org 2009-04-11 10:32 --- Fixed with r145955. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39692
[Bug fortran/39692] f95: conflict between EXTERNAL and POINTER
-- janus at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |janus at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2009-04-11 10:32:00 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39692
[Bug fortran/39692] f95: conflict between EXTERNAL and POINTER
--- Comment #2 from janus at gcc dot gnu dot org 2009-04-11 10:30 --- Subject: Bug 39692 Author: janus Date: Sat Apr 11 10:30:29 2009 New Revision: 145955 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145955 Log: 2009-04-11 Janus Weil PR fortran/39692 * symbol.c (check_conflict): Reject procedure pointers for -std=f95. 2009-04-11 Janus Weil PR fortran/39692 * gfortran.dg/proc_ptr_14.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/proc_ptr_14.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/symbol.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39692
[Bug middle-end/39732] [4.5 Regression] -fprofile-generate -O1: ICE: verify_stmts failed, ADDRESSABLE bit not set on pointers passed to std::copy
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-04-11 10:20 --- Subject: Bug 39732 Author: rguenth Date: Sat Apr 11 10:19:55 2009 New Revision: 145954 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145954 Log: 2009-04-11 Richard Guenther PR middle-end/39732 * tree-inline.c (declare_return_variable): Mark DECL_BY_REFERENCE return variables as TREE_ADDRESSABLE. * g++.dg/torture/pr39732.C: New testcase. Added: trunk/gcc/testsuite/g++.dg/torture/pr39732.C Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-inline.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39732
[Bug middle-end/39732] [4.5 Regression] -fprofile-generate -O1: ICE: verify_stmts failed, ADDRESSABLE bit not set on pointers passed to std::copy
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-04-11 10:20 --- Fixed. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39732
[Bug fortran/25104] [F2003] Non-initialization expr. as case-selector
--- Comment #15 from dfranke at gcc dot gnu dot org 2009-04-11 08:33 --- > Could the patches in comments #11 to #13 be applied to trunk too? They can and will, but there are at least two more coming and I want to have and test them together before moving them over to trunk. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25104
[Bug middle-end/39732] [4.5 Regression] -fprofile-generate -O1: ICE: verify_stmts failed, ADDRESSABLE bit not set on pointers passed to std::copy
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-04-11 08:13 ---
template struct char_traits;
template
_OI __copy_move_a2(_OI __result);
template inline _OI
copy(_OI __result)
{
return __copy_move_a2 (__result);
}
template
class basic_ostream { };
template >
class ostream_iterator {
typedef basic_ostream<_CharT, _Traits> ostream_type;
ostream_type* _M_stream;
const _CharT* _M_string;
public:
ostream_iterator(ostream_type& __s, const _CharT* __c)
: _M_stream(&__s), _M_string(__c) { }
ostream_iterator(const ostream_iterator& __obj)
: _M_stream(__obj._M_stream), _M_string(__obj._M_string) { }
};
int f(void)
{
basic_ostream > os;
copy(ostream_iterator(os, ","));
}
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Component|gcov-profile|middle-end
Ever Confirmed|0 |1
Keywords||ice-on-valid-code
Last reconfirmed|-00-00 00:00:00 |2009-04-11 08:13:13
date||
Summary|-fprofile-generate -O1: ICE:|[4.5 Regression] -fprofile-
|verify_stmts failed,|generate -O1: ICE:
|ADDRESSABLE bit not set on |verify_stmts failed,
|pointers passed to std::copy|ADDRESSABLE bit not set on
||pointers passed to std::copy
Target Milestone|--- |4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39732
[Bug tree-optimization/39713] [4.4/4.5 Regression] ICE in get_expr_value_id
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-04-11 07:44 --- Fixe.d -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39713
[Bug gcov-profile/39732] -fprofile-generate -O1: ICE: verify_stmts failed, ADDRESSABLE bit not set on pointers passed to std::copy
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-04-11 07:47 --- Reducing. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39732
[Bug c/39712] [4.5 Regression] type mismatch in address expression
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-04-11 07:44 --- Fixed. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39712
[Bug tree-optimization/39713] [4.4/4.5 Regression] ICE in get_expr_value_id
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-04-11 07:43 --- Subject: Bug 39713 Author: rguenth Date: Sat Apr 11 07:42:52 2009 New Revision: 145952 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145952 Log: 2009-04-11 Richard Guenther PR tree-optimization/39713 * tree-ssa-sccvn.c (vn_get_expr_for): Make sure built reference trees have SSA_NAME operands. * g++.dg/torture/pr39713.C: New testcase. Added: branches/gcc-4_4-branch/gcc/testsuite/g++.dg/torture/pr39713.C Modified: branches/gcc-4_4-branch/gcc/ChangeLog branches/gcc-4_4-branch/gcc/testsuite/ChangeLog branches/gcc-4_4-branch/gcc/tree-ssa-sccvn.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39713
[Bug c/21920] aliasing violations
--- Comment #140 from pinskia at gcc dot gnu dot org 2009-04-11 07:20 --- *** Bug 39734 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||vkolluri at cisco dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21920
[Bug tree-optimization/39713] [4.4/4.5 Regression] ICE in get_expr_value_id
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-04-11 07:34 --- Subject: Bug 39713 Author: rguenth Date: Sat Apr 11 07:34:09 2009 New Revision: 145951 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145951 Log: 2009-04-11 Richard Guenther PR tree-optimization/39713 * tree-ssa-sccvn.c (vn_get_expr_for): Make sure built reference trees have SSA_NAME operands. * g++.dg/torture/pr39713.C: New testcase. Added: trunk/gcc/testsuite/g++.dg/torture/pr39713.C Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-sccvn.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39713
[Bug c/39712] [4.5 Regression] type mismatch in address expression
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-04-11 07:33 --- Subject: Bug 39712 Author: rguenth Date: Sat Apr 11 07:32:52 2009 New Revision: 145950 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145950 Log: 2009-04-11 Richard Guenther PR c/39712 * c-gimplify.c (c_gimplify_expr): Adjust check for mismatched address expressions. * gcc.dg/pr39712.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/pr39712.c Modified: trunk/gcc/ChangeLog trunk/gcc/c-gimplify.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39712
[Bug c/39734] Misordering of instructions for short moves in a C program
--- Comment #4 from pinskia at gcc dot gnu dot org 2009-04-11 07:20 ---
u_int32_t mask[1] = { 0x };
u_int32_t cfg[1] = { 0x };
u_int16_t *cfg16 = (u_int16_t *)cfg;
u_int16_t *mask16 = (u_int16_t *)mask;
printf("mask16[0]: 0x%04x\n", mask16[0]);
You are violating C/C++ aliasing rules as you are accessing a u_int32_t as a
u_int16_t.
*** This bug has been marked as a duplicate of 21920 ***
--
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=39734
