[Bug c/42643] "may be used uninitialized" compiled with "-Wall -O"

2012-01-06 Thread mi+gcc at aldan dot algebra.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42643 --- Comment #2 from mi+gcc at aldan dot algebra.com 2012-01-06 20:08:54 UTC --- Created attachment 26259 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26259 Live test case (file from Mozilla's NSS package) Even when using gcc-4

[Bug fortran/87341] New: gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-17 Thread mi+gcc at aldan dot algebra.com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: mi+gcc at aldan dot algebra.com Target Milestone: --- The entire gcc-8.2 configured with the following: ./configure --enable-cxx --enable-alloca --prefix=/prod/pfe/local --with

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-17 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #1 from mi+gcc at aldan dot algebra.com --- Invoking gfortran with -v I get the following details: Driving: gfortran -v -o xscblat1 c_sblat1.o c_sblas1.o ../lib/cblas_LINUX.a -l gfortran -l m -shared-libgcc Using built-in specs

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-17 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #2 from mi+gcc at aldan dot algebra.com --- BTW, I'd dearly love if not a fix, then a work-around ASAP. Is there some kind of command-line option I can add to gfortran's command-line? Thanks!

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-17 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #4 from mi+gcc at aldan dot algebra.com --- (In reply to Andrew Pinski from comment #3) > This is a binutils bug, in gold. > --enable-gold > > Please report this to binutils instead. Is there a work-around, perhaps? Som

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-18 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 mi+gcc at aldan dot algebra.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-18 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #9 from mi+gcc at aldan dot algebra.com --- > I said binutils 2.31 branch, not 2.31 release. The work I'm doing is meant for eventual production use. The company has swallowed the use of free software, but using _unreleased_

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-18 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #10 from mi+gcc at aldan dot algebra.com --- (In reply to mi+gcc from comment #9) > Is this it, for example: > > https://sourceware.org/ml/binutils/2018-08/msg00227.html Applied the patch to the 2.31 release

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-18 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #12 from mi+gcc at aldan dot algebra.com --- (In reply to H.J. Lu from comment #11) > Please show the output of: > > $ objdump -T > /prod/pfe/local/lib/gcc/x86_64-pc-linux-gnu/8/../../../../lib64/libgfortran. > so

[Bug fortran/87341] gfortran can not link executables: _edata: invalid version 21 (max 4)

2018-09-18 Thread mi+gcc at aldan dot algebra.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87341 --- Comment #14 from mi+gcc at aldan dot algebra.com --- (In reply to H.J. Lu from comment #13) > Please try binutils 2.31 branch from: > > https://sourceware.org/git/?p=binutils-gdb.git;a=shortlog;h=refs/heads/ > binutils-2_31-branc

[Bug middle-end/62029] New: Requesting new warning: missing const-qualifier

2014-08-05 Thread mi+gcc at aldan dot algebra.com
Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: mi+gcc at aldan dot algebra.com To help facilitate "const-poisoning" of the entire body of C (and C++) code out there, I'd like to see a new warning, that would fire, when a pointer to any obje

[Bug c/108768] New: bogus -Warray-bounds warnings

2023-02-12 Thread mi+gcc at aldan dot algebra.com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: mi+gcc at aldan dot algebra.com Target Milestone: --- Created attachment 54453 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54453&action=edit Test case (otpcode.c after passing preprocessor) Compiling the attached file (