[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #9 from Joshua Cogliati --- Looking at write.c, there are multiple places where things like the pattern: result = select_string (dtp, f, str_buf, &res_len, kind); ... get_float_string (dtp, f, source , kind, 0, buffer,

[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #8 from Joshua Cogliati --- Created attachment 44186 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44186&action=edit Patch by keeping original length This patches the problem by storing the allocated length in a separate varia

[Bug fortran/85840] Memory leak in write.c

2018-05-25 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #7 from Joshua Cogliati --- Created attachment 44185 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44185&action=edit Patch by checking against original buffer This is one possible patch for this problem, it just checks if the

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #4 from Joshua Cogliati --- And to replicate it with the simple program: gfortran -Wall -g -o simple simple.f90 valgrind --leak-check=full ./simple and you get things like: ==19171== 323 bytes in 1 blocks are definitely lost in

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 --- Comment #3 from Joshua Cogliati --- Created attachment 44150 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44150&action=edit simple program to demonstrate problem

[Bug fortran/85840] Memory leak in write.c

2018-05-20 Thread jjcogliati-r1 at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840 Joshua Cogliati changed: What|Removed |Added CC||jjcogliati-r1 at yahoo dot com

[Bug fortran/85840] New: Memory leak in write.c

2018-05-18 Thread jjcogliati-r1 at yahoo dot com
Assignee: unassigned at gcc dot gnu.org Reporter: jjcogliati-r1 at yahoo dot com Target Milestone: --- This bug comes from trying to find a memory leak in my own program. gfortran --version GNU Fortran (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5) Copyright (C) 2017 Free Software Foundation, Inc

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-11-22 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #30 from Joshua Cogliati --- Yes, it is fixed so far as I am concerned. I checked out gcc trunk 205109, and bootstraped it and tried it out on: int main(int argc, char ** argv) { int i = 3.14; return i; } int foo(double x) { r

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-10-27 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #27 from Joshua Cogliati --- Created attachment 31097 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31097&action=edit Patch to add -Wfloat-conversion option against trunk with new testcase and detailed warnings This uses a detai

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-10-21 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #26 from Joshua Cogliati --- Created attachment 31065 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31065&action=edit Patch to add -Wfloat-conversion option against trunk with new testcase This adds a new testcase instead of usi

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-10-13 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added Attachment #30979|0 |1 is obsolete|

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-10-10 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #23 from Joshua Cogliati --- Created attachment 30980 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30980&action=edit Patch to fixup gcc float conversions in GCC This changes the float conversions in gcc so that gcc bootstraps i

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-10-10 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added Attachment #30899|0 |1 is obsolete|

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-30 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added Attachment #30913|0 |1 is obsolete|

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-27 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #19 from Joshua Cogliati --- Created attachment 30913 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30913&action=edit Patch to add -Wfloat-conversion option against trunk This version is against gcc trunk (rev 202818). It now b

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-26 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #18 from Joshua Cogliati --- (In reply to Manuel López-Ibáñez from comment #17) > (In reply to Joshua Cogliati from comment #16) > > This does not bootstrap trunk yet, because gcc has floating conversion > > issues and with this being

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-25 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added Attachment #30873|0 |1 is obsolete|

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-22 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added Attachment #30870|0 |1 is obsolete|

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #14 from Joshua Cogliati --- Manuel López-Ibáñez, thank you for the patch review. I will make the changes you requested, and rebase it against svn trunk, and run bootstrap and testsuite. It may be a few weeks before I get this all do

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #11 from Joshua Cogliati --- Created attachment 30873 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30873&action=edit Patch to add -Wfloat-conversion option This version also is enabled with -Wextra. $ gcc -o float_test float

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #9 from Joshua Cogliati --- Created attachment 30871 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30871&action=edit some floating conversion issues This tests three of the floating conversion reduction in precision issues. P

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Joshua Cogliati changed: What|Removed |Added CC||jjcogliati-r1 at yahoo dot com

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2013-09-02 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #7 from Joshua Cogliati --- I wrote the patch for 4.8.1 (which is the easy part), now I will see if I can get approval to submit it through the bureaucracies (the hard part).

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2012-06-22 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #5 from Joshua Cogliati 2012-06-22 12:29:14 UTC --- (In reply to comment #3) > (In reply to comment #2) > > I should have time to create a patch for this before 4.8 goes into stage 3. > > Do > > you think it needs a copyright assign

[Bug c/53001] -Wfloat-conversion should be available to warn about floating point errors

2012-04-16 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 --- Comment #2 from Joshua Cogliati 2012-04-16 12:16:45 UTC --- Yes, it should also warn for non-constants, and also for other floating decreases in accuracy such as: float foo(double x) { return x; } I should have time to create a patch for

[Bug c/53001] New: -Wfloat-conversion should be available to warn about floating point errors

2012-04-15 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53001 Bug #: 53001 Summary: -Wfloat-conversion should be available to warn about floating point errors Classification: Unclassified Product: gcc Version: unknown Status: UN

[Bug fortran/49324] Deep copy missing for array constructors of DT w/ allocatable components

2011-07-11 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49324 Joshua Cogliati changed: What|Removed |Added Known to fail||4.6.1 --- Comment #11 from Joshua Cogli

[Bug fortran/49324] iso_varying_string and reshape fail

2011-06-08 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49324 --- Comment #2 from Joshua Cogliati 2011-06-08 16:30:16 UTC --- (In reply to comment #1) > Not an analysis, just some observations ... > > I get different results with different compilers: > gfortran 4.7: > array2d second2

[Bug fortran/49324] New: iso_varying_string and reshape fail

2011-06-08 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49324 Summary: iso_varying_string and reshape fail Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassig...@g

[Bug c++/47367] internal compiler error: verify_cgraph_node failed

2011-01-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47367 Joshua Cogliati changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|

[Bug c++/47367] internal compiler error: verify_cgraph_node failed

2011-01-20 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47367 Joshua Cogliati changed: What|Removed |Added CC||jjcogliati-r1 at yahoo dot

[Bug c++/47367] New: internal compiler error: verify_cgraph_node failed

2011-01-19 Thread jjcogliati-r1 at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47367 Summary: internal compiler error: verify_cgraph_node failed Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: u

[Bug libfortran/43298] fortran library does not read in NaN -Inf or Inf

2010-03-08 Thread jjcogliati-r1 at yahoo dot com
--- Comment #1 from jjcogliati-r1 at yahoo dot com 2010-03-08 21:17 --- program should be: (both exhibit the bug though, but this works if bug is not present) program nan_test implicit none character(15) :: nan = ' NAN -INF INF' real :: a,b,c, d = 0.

[Bug libfortran/43298] New: fortran library does not read in NaN -Inf or Inf

2010-03-08 Thread jjcogliati-r1 at yahoo dot com
gnu dot org ReportedBy: jjcogliati-r1 at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43298

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-13 Thread jjcogliati-r1 at yahoo dot com
--- Comment #15 from jjcogliati-r1 at yahoo dot com 2010-01-13 23:27 --- (In reply to comment #14) > I am testing the workaround > > Index: gcc/gimple.c > === > --- gcc/gimple.c(revision 155860) >

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-12 Thread jjcogliati-r1 at yahoo dot com
--- Comment #12 from jjcogliati-r1 at yahoo dot com 2010-01-12 21:14 --- (In reply to comment #10) > Subject: Re: Internal compiler exception in with gfortran > when using -fwhole-program -flto -fopenmp > > On Mon, 11 Jan 2010, jjcogliati-r1 at yahoo d

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-11 Thread jjcogliati-r1 at yahoo dot com
--- Comment #11 from jjcogliati-r1 at yahoo dot com 2010-01-11 18:58 --- (In reply to comment #10) > Subject: Re: Internal compiler exception in with gfortran > when using -fwhole-program -flto -fopenmp > > On Mon, 11 Jan 2010, jjcogliati-r1 at yahoo d

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-11 Thread jjcogliati-r1 at yahoo dot com
--- Comment #9 from jjcogliati-r1 at yahoo dot com 2010-01-11 17:15 --- My hunch, (and I could be wrong since my knowledge of gcc's tree code was zero as of Friday morning) is that it is trying to find the array's min and max size, but that only the min location is available

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-11 Thread jjcogliati-r1 at yahoo dot com
--- Comment #7 from jjcogliati-r1 at yahoo dot com 2010-01-11 15:50 --- (In reply to comment #6) > Try > > Index: gcc/gimple.c > === > --- gcc/gimple.c(revision 155739) > +++ gcc/gimple.c

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-08 Thread jjcogliati-r1 at yahoo dot com
--- Comment #5 from jjcogliati-r1 at yahoo dot com 2010-01-08 22:28 --- (In reply to comment #4) > Subject: Re: Internal compiler exception in with gfortran > when using -fwhole-program -flto -fopenmp > > On Fri, 8 Jan 2010, jjcogliati-r1 at yahoo d

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-08 Thread jjcogliati-r1 at yahoo dot com
--- Comment #3 from jjcogliati-r1 at yahoo dot com 2010-01-08 21:38 --- (In reply to comment #1) > Can you run it in a debugger and print what 'code' actually is? Can you > check if removing -g fixes the ICE? > Code is: ERROR_MARK (gdb) break tree.c:6592 Break

[Bug lto/42665] Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-08 Thread jjcogliati-r1 at yahoo dot com
--- Comment #2 from jjcogliati-r1 at yahoo dot com 2010-01-08 21:27 --- (In reply to comment #1) > Can you run it in a debugger and print what 'code' actually is? Can you > check if removing -g fixes the ICE? > The ICE still happens when -g is removed. I'm w

[Bug lto/42665] New: Internal compiler exception in with gfortran when using -fwhole-program -flto -fopenmp

2010-01-08 Thread jjcogliati-r1 at yahoo dot com
erity: normal Priority: P3 Component: lto AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jjcogliati-r1 at yahoo dot com GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linu

[Bug libfortran/38097] New: gfortran does not allow blanks in exponent in float (even with BN)

2008-11-12 Thread jjcogliati-r1 at yahoo dot com
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jjcogliati-r1 at yahoo dot com GCC build triplet: x86_64-redhat

[Bug bootstrap/29316] gcc-4.1.1 fails to bootstrap again

2006-11-12 Thread jjcogliati-r1 at yahoo dot com
--- Comment #3 from jjcogliati-r1 at yahoo dot com 2006-11-13 04:35 --- (In reply to comment #2) > Use --disable-multilib as ppc-darwin is configured by default to also build > the > 64bit libraries. > Why is this not a bug? --disable-multilib is not mentioned in http:/

[Bug fortran/27470] [4.1 regression] wrong memory allocator for derived types

2006-06-28 Thread jjcogliati-r1 at yahoo dot com
--- Comment #14 from jjcogliati-r1 at yahoo dot com 2006-06-28 18:02 --- This works in 4.1.0, so only 4.1.1 has this bug so far as I can tell. -- jjcogliati-r1 at yahoo dot com changed: What|Removed |Added

[Bug fortran/23375] show location for runtime errors

2006-05-24 Thread jjcogliati-r1 at yahoo dot com
--- Comment #5 from jjcogliati-r1 at yahoo dot com 2006-05-24 12:49 --- (In reply to comment #4) > (In reply to comment #3) > > > So in GCC 4.1.0, the only problem seems to be that _gfortran_runtime_error > > is > > not printing the filename and the line nu

[Bug fortran/23375] show location for runtime errors

2006-05-10 Thread jjcogliati-r1 at yahoo dot com
--- Comment #3 from jjcogliati-r1 at yahoo dot com 2006-05-10 13:54 --- (In reply to comment #1) > Confirmed. Though sometimes I wonder if this is an over use of printf style > debugging. > Well, I have a fortran program. It ran fine for the first 10 and a half hours. The

[Bug fortran/26791] New: Array reference out of bounds runtime error should print more information

2006-03-21 Thread jjcogliati-r1 at yahoo dot com
: jjcogliati-r1 at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26791

[Bug fortran/26787] New: Assigning to function causes ice in gfortran

2006-03-21 Thread jjcogliati-r1 at yahoo dot com
Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jjcogliati-r1 at yahoo dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug fortran/26682] New: gfortran fails with -fwhole-program optimization

2006-03-14 Thread jjcogliati-r1 at yahoo dot com
n AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jjcogliati-r1 at yahoo dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26682