regressions tests fine on x86-64.
Test case is that provided in the PR.
OK for trunk?
Regards,
Jerry
2011-04-17 Jerry DeLisle
PR libgfortran/48602
* io/write_float.def (output_float_FMT_G): Use current rounding mode
to set the rounding parameters. (output_float): Skip
On 04/17/2011 11:39 AM, Steve Kargl wrote:
On Sun, Apr 17, 2011 at 10:14:37AM -0700, Jerry DeLisle wrote:
Hi Folks,
This patch implements the adjustments required for the various rounding
modes as stated in the Fortran Standard F2008, paragraph 10.7.5.2.2. In
the process of testing this patch
Committed the following after regression testing. i will update the test case
when I get the chance.
Jerry
Author: jvdelisle
Date: Wed Apr 20 04:18:25 2011
New Revision: 172753
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172753
Log:
2011-04-19 Jerry DeLisle
PR lib
On 04/22/2011 02:48 PM, Tobias Burnus wrote:
Another two simple coarray fixes:
(a) when reading a module, the cotype was not set. The consequence was that one
could not use associate alloctable coarray module variables
(b) The coindexed check was overeager and also rejected "alloctate( x%b(3)[*
Log summarizes. One new test case is
added.
OK for trunk?
Regards,
Jerry
2011-04-24 Jerry DeLisle
PR libgfortran/48488
PR libgfortran/48602
PR libgfortran/48615
PR libgfortran/48684
* io/write.c (set_fnode_default): Adjust default widths to assure
On 04/25/2011 03:48 AM, Janne Blomqvist wrote:
On Sun, Apr 24, 2011 at 23:32, Jerry DeLisle wrote:
The final solution to 48602 I want to do as a second phase to this. The
second phase will attempt to avoid floating point comparisons which are
sensitive to optimizations and or printf behavior
On 04/23/2011 08:22 AM, Thomas Koenig wrote:
Hello world,
the attached patch puts temporary variables, and the statement they are being
generated for, in their own BLOCK.
This may or may not be useful for data locality, and for telling the middle end
explicitly about the lifetime of the tempora
On 04/25/2011 07:36 AM, Janne Blomqvist wrote:
On Mon, Apr 25, 2011 at 14:44, Jerry DeLisle wrote:
On 04/25/2011 03:48 AM, Janne Blomqvist wrote:
Now, for one of the testcase changes:
--- gcc/testsuite/gfortran.dg/char4_iunit_1.f03 (revision 172909)
+++ gcc/testsuite/gfortran.dg
On 04/25/2011 07:36 AM, Janne Blomqvist wrote:
On Mon, Apr 25, 2011 at 14:44, Jerry DeLisle wrote:
On 04/25/2011 03:48 AM, Janne Blomqvist wrote:
Now, for one of the testcase changes:
--- gcc/testsuite/gfortran.dg/char4_iunit_1.f03 (revision 172909)
+++ gcc/testsuite/gfortran.dg
On 04/26/2011 09:09 PM, Jerry DeLisle wrote:
---snip---
1.234500019E-06 4284600.00
1.234500019E-06 4284600.00
1.23450002E-06 4284600.00
And without the patch:
1.23450002E-06 4284600.00
1.234500019E-06 4284600.00
1.23450002E-06 4284600.00
d is
On 04/27/2011 12:57 PM, Janne Blomqvist wrote:
On Wed, Apr 27, 2011 at 08:53, Janne Blomqvist
wrote:
On Wed, Apr 27, 2011 at 07:09, Jerry DeLisle wrote:
On 04/25/2011 07:36 AM, Janne Blomqvist wrote:
On Mon, Apr 25, 2011 at 14:44, Jerry DeLisle
wrote:
On 04/25/2011 03:48 AM, Janne
On 04/28/2011 04:18 PM, Tobias Burnus wrote:
The attached patch fixes two regressions:
a) PR 48810: For type-bound procedures, the access flags should be checked only
for the generic function, not for the specific function the generic resolves to.
(4.6/4.7 rejects-valid regression.)
b) PR 48800
On 04/29/2011 08:20 AM, Janne Blomqvist wrote:
Hello all,
since about a decade or so ago, POSIX specifies that PATH_MAX includes
the trailing null byte (previously it was undefined). However,
libgfortran has incorrectly assumed the opposite, and has thus created
temporary buffers of length PATH_
enchilada to 4.6.1 in a few
weeks. Please consider the starting point of the zero scan carefully. I have
not convinced myself that the d * p covers all cases, but it works for all cases
I have tried.
Regards,
Jerry
2011-04-29 Jerry DeLisle
PR libgfortran/48787
* io
On 04/30/2011 12:56 AM, Janne Blomqvist wrote:
On Sat, Apr 30, 2011 at 04:33, Jerry DeLisle wrote:
Hi,
The attached patch does some cleanup and a check for trailing zeros to
decide whether or not to round.
I have added the additional test cases posted on the bugzilla to the
existing test
Committed revision 173218.
Regression tested on x86-64.
Author: jvdelisle
Date: Sat Apr 30 15:24:57 2011
New Revision: 173218
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173218
Log:
2011-04-30 Jerry DeLisle
Backport from mainline:
PR libgfortran/48030
* i
On 04/29/2011 02:45 PM, Tobias Burnus wrote:
Nearly obvious patch. Build and regtested on x86-64-linux.
OK for the trunk?
Tobias
Thats a oneliner. OK
Thanks,
Jerry
On 05/02/2011 07:20 AM, Rainer Orth wrote:
gfortran.dg/fmt_g0_6.f08 execution seems to fail on all 32-bit x86
targets at -O1 and above. Running it under gdb, I find
Program received signal SIGABRT, Aborted.
[Switching to Thread 1 (LWP 1)]
0xfed0ff85 in _lwp_kill () from /lib/libc.so.1
(gdb) whe
On 05/03/2011 03:14 AM, Tobias Burnus wrote:
Rainer,
Rainer Orth wrote:
Jerry DeLisle wrote:
This is OK. We are working on a solution, so maybe it would be better to
XFAIL it so that when it does get fixed it will be flagged. It also fails
on i686-pc-gnu.
is this a solution for this
ched.
OK for trunk?
Jerry
2011-05-03 Jerry DeLisle
PR libgfortran/48787
* io/write_float.def (output_float): Adjust up and down rounding for
cases where 'd' = 0. Gather common code to one location.
On 05/04/2011 10:45 PM, Tobias Burnus wrote:
This patch does the first minor steps towards TR 29113: It accepts the OPTIONAL
attribute in procedures with C binding. As gfortran already passes absent
arguments a NULL pointer, there is no changed needed, except in the diagnostics
part. Additionally
On 05/03/2011 11:31 PM, Tobias Burnus wrote:
The global variables generated to store this_image/num_images were wrong in
several ways:
- translation-unit (TU) dependent name (could be same or different)
- variable generated in every TU - and not only in one
- not pushed - which could cause alrea
On 05/01/2011 02:49 AM, Thomas Koenig wrote:
Hello world,
after Paul's fix for allocate on assignment (thanks Paul!), here is a
patch for the original test case from PR 22572, where the bounds of
the function are unknown at compile time. This uses an allocatable
temporary.
In the long run, anot
On 05/14/2011 06:47 AM, Tobias Burnus wrote:
This patch re-adds the option -f(no-)backtrace as Ignored to improve backward
compatibility.
Additionally, for ERROR STOP, no backtrace is printed any more.
Build on x86-64-linux.
OK for the trunk?
Tobias
OK, thanks,
Jerry
On 03/06/2011 10:57 AM, Paul Richard Thomas wrote:
This one was exceedingly difficult to diagnose. The workings of
array.c are opaque to say the least of it! However, the fix is
relatively clear. The testcase in the PR failed because the argument
of ANY is not a gfc_constant_ac. However, iter
On 03/12/2011 03:16 AM, Janus Weil wrote:
Hi all,
the attached patch fixes the PR in the subject line. The problem was
the following: During the interface mapping for a procedure call we
need to take special care of polymorphic arguments, since the type of
the actual argument can differ from the
On 03/12/2011 08:01 AM, John David Anglin wrote:
I have reviewed the patch and FX'scomments. So far so good.
I may have missed something in the thread, but are you planning
modifications to the functions that call convert_real to allow the nan
or inf strings to be passed to convert_real?
The r
On 03/12/2011 07:21 AM, FX wrote:
The attached patch fixes half of PR 47439. On platform with weak or historical
implementations of mktemp(), this function cannot generate more than 26 unique
filenames for a given base. This happens in particular on Windows, and limits
us to 26 scratch files o
On 03/12/2011 02:09 PM, Thomas Koenig wrote:
Hello world,
the attached patch fixes PR 48066, a regression introduced way back when. It is
pretty self-explanatory. Regression-tested.
OK for trunk?
OK and thanks for patch!
Jerry
On 03/12/2011 02:04 PM, Jerry DeLisle wrote:
On 03/12/2011 08:01 AM, John David Anglin wrote:
I have reviewed the patch and FX'scomments. So far so good.
I may have missed something in the thread, but are you planning
modifications to the functions that call convert_real to allow the n
On 03/12/2011 03:04 PM, Mikael Morin wrote:
On Saturday 12 March 2011 23:40:32 Thomas Koenig wrote:
Hi Jerry,
On 03/12/2011 02:09 PM, Thomas Koenig wrote:
Hello world,
the attached patch fixes PR 48066, a regression introduced way back
when. It is
pretty self-explanatory. Regression-tested.
Hi,
The attached patch re-implements read_x using fbuf_getc. Self explanatory.
Regression tested on x86-64 linux. No new test case needed.
Ok for trunk?
Regards,
Jerry
2011-03-19 Jerry DeLisle
PR libgfortran/48030
* io/read.c (read_x): Re-implement using fbuf_getc
I have completed a merge of trunk into the branch.
Committed revision 171203.
Regards,
Jerry
Ping
On 03/19/2011 09:46 PM, Jerry DeLisle wrote:
Hi,
The attached patch re-implements read_x using fbuf_getc. Self explanatory.
Regression tested on x86-64 linux. No new test case needed.
Ok for trunk?
Regards,
Jerry
2011-03-19 Jerry DeLisle
PR libgfortran/48030
* io/read.c (read_x
On 03/22/2011 06:19 AM, Janne Blomqvist wrote:
On Tue, Mar 22, 2011 at 03:15, Jerry DeLisle wrote:
Ping
On 03/19/2011 09:46 PM, Jerry DeLisle wrote:
Hi,
The attached patch re-implements read_x using fbuf_getc. Self explanatory.
I suspect this doesn't actually fix the issue with re
On 03/24/2011 06:10 AM, Nathan Froyd wrote:
The Fortran-specific bits of these patches:
[PATCH 02/18] enforce TREE_CHAIN and TREE_TYPE accesses
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg00565.html
[PATCH 07/18] generalize build_case_label to the rest of the compiler
http://gcc.gn
On 03/26/2011 04:49 AM, Tobias Burnus wrote:
ping**2
On 24.03.2011 16:54, Tobias Burnus wrote:
*ping*
http://gcc.gnu.org/ml/fortran/2011-03/msg00162.html
(RFC patch: http://gcc.gnu.org/ml/fortran/2011-03/msg3.html)
Tobias
PS: I will come back to the other emails of this week tomorrow; I
On 03/31/2011 01:28 PM, Thomas Koenig wrote:
Hello world,
the attached patch fixes a 4.7 regression, PR 48352, where a function
elimination in the expressions for a DO loop caused an ICE. The ICE was caused
by interaction of the expression walker with insertion of a statement for a DO
loop.
Man
On 03/28/2011 11:50 AM, Thomas Koenig wrote:
Hello world,
the attached patch extends the character optimizations to the lexical comparison
functions (LLE and friends).
Regression-tested. OK for trunk?
Yes, this patch is OK?
Thanks,
Jerry
On 04/01/2011 06:29 AM, Jerry DeLisle wrote:
On 03/28/2011 11:50 AM, Thomas Koenig wrote:
Hello world,
the attached patch extends the character optimizations to the lexical comparison
functions (LLE and friends).
Regression-tested. OK for trunk?
Yes, this patch is OK?
Fat fingers, s
Good to go.
On Fri, Oct 11, 2024, 9:06 AM Thomas Koenig wrote:
> Am 11.10.24 um 18:00 schrieb Thomas Koenig:
> > Hello world,
> >
> > the attached patch creates an unsigned "standard" for the
> > gfc_option.allow_std field.
> >
> > One of the main reason why people want UNSIGNED for Fortran is
>
Thanks Paul, got it.
On Mon, Nov 25, 2024, 3:13 AM Paul Richard Thomas <
paul.richard.tho...@gmail.com> wrote:
> Hi Jerry,
>
> OK by me.
>
> A small nit: s/too/to/ in the ChangeLog.
>
> Thanks for the patch
>
> Paul
>
>
> On Mon, 25 Nov 2024 at 02:50, Jerry D wrote:
>
>> I would like to commit t
Looks good, OK to push.
On Sun, Dec 8, 2024, 1:39 PM Harald Anlauf wrote:
> Dear all,
>
> while looking at testcases with inquiry refs, I encountered two minor
> GMP memleaks due to double-initialization of GMP variables. Easily
> plugged by the attached patch.
>
> Regtested on x86_64-pc-linux-
Thanks Paul.
Regards, Jerry
On Tue, Dec 17, 2024, 12:34 AM Paul Richard Thomas <
paul.richard.tho...@gmail.com> wrote:
> Hi All,
>
> This bug was so obviously in defiance of the standard that I pushed it to
> mainline as r15-6260. I meant to post this message immediately but was
> distracted bef
I got as far as applying and regression testing version 2. I have queried
around for others to look over the patch. I will scan this one.
Since you are the expert in this area, we may just have you push and let
the pieces fall out.
I will get back to you later today.
Jerry
On Fri, Dec 20, 2024,
Looks Ok by me.
Thanks,
Jerry
On Fri, Jan 17, 2025, 12:25 PM Harald Anlauf wrote:
> Dear all,
>
> the attached obvious patch extends G formatting to UNSIGNED by reusing
> the code for I formatting.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> Thanks,
> Harald
>
>
Committed as obvious:
commit 061b13ed014ba0b6891800a5c7f852bf58e4d856
Author: Jerry DeLisle
Date: Thu Feb 16 18:13:56 2023 -0800
Fortran Tests: Allow passing on mingw.
gcc/testsuite/ChangeLog:
* gfortran.dg/bind_c_array_params_2.f90: Add *-*-ming* to
dg-final.
and
ok, thanks .
On 9/15/20 1:35 PM, Harald Anlauf wrote:
As stated in the PR, the Fortran 2018 standard removed the restriction
prohibiting ELEMENTAL RECURSIVE procedures. Adjust the relevant check.
Regtested on x86_64-pc-linux-gnu.
OK for master?
Thanks,
Harald
PR fortran/97036 - [F2018] All
Harold, Looks good. Thanks for the work!
Jerry
On 9/20/20 11:10 AM, Harald Anlauf wrote:
*ping*
Gesendet: Sonntag, 13. September 2020 um 23:24 Uhr
Von: "Harald Anlauf"
An: "fortran" , "gcc-patches"
Cc: "Paul Richard Thomas"
Betreff: [PATCH] PR fortran/90903 [part2] Add runtime checking for
The attached patch was provided by Steve Kargl. After exploring for
possible other checks I settled on leaving the patch intact.
Two existing test cases updated as different but sensible error messages
resulted.
Regression tested on main line.
OK to commit?
Regards,
Jerry
Author: Steve Kargl
This look good, OK to commit.
Thanks,
Jerry
On 8/10/20 8:03 AM, Andre Vehreschild wrote:
Hi folks,
long time, no see. I was asked by Damian to do some Coarray stuff in gfortran
so here is the first step on fixing a bug. The issue at hand is, that the
coarray handling is not propagated correc
On 8/17/20 12:31 AM, Mark Eggleston wrote:
Please find attached a patch for PR96436.
OK to commit?
Looks good to me. Thanks for fixing this.
Regards,
Jerry
OK to commit and backport.
On 6/30/20 11:12 PM, Mark Eggleston wrote:
Please find attached a patch which is a fix for PR95612. The original
patch is by Steve Kargl.
OK to commit and backport?
Commit message:
Fortran : ICE in gfc_check_pointer_assign PR95612
Output an error if the right ha
OK to commit and Backport.
On 6/18/20 1:11 AM, Mark Eggleston wrote:
Please find attached fix for PR95585.
OK to commit and backport?
Commit message:
Fortran : ICE in gfc_check_reshape PR95585
Issue an error where an array is used before its definition
instead of an ICE.
2020-06-18 Steven
LGTM Paul, go for it.
On 12/26/20 8:37 AM, Paul Richard Thomas via Fortran wrote:
Ping!
On Sat, 12 Dec 2020 at 10:38, Paul Richard Thomas <
paul.richard.tho...@gmail.com> wrote:
Fortran: Fix some select rank issues [PR97694 and 97723].
Hi All,
Unlike select type, select rank selectors retai
Looks good and I have tested. I will commit after one more double check
for regressions with the test case in the testsuite
I have been following Harris on this one for several days and tested the
patch before submitted here.
Thanks for patch Harris, much appreciated.
Regards,
Jerry
On 1/1
OK, and thanks for Patch.
On 6/23/20 2:08 PM, Harald Anlauf wrote:
Dear all,
here's another case with a buffer that did overflow.
Regtested on x86_64-pc-linux-gnu.
OK for master / backports?
Thanks,
Harald
PR fortran/95827 - Buffer overflows with PDTs and long symbols
With submodules and
OK, and once again, thanks.
Jerry
On 6/17/20 12:27 PM, Harald Anlauf wrote:
Another corner case of buffer overflows during name mangling found by
Gerhard. We now check that the new buffer sizes suffice.
The patch is on top of the patches for PRs 95687, 95688, 95689.
Regtested on x86_64-pc-lin
On 6/27/20 1:40 AM, Thomas Koenig via Fortran wrote:
Hi Mark,
Use -fdec-add-missing-indexes to enable feature. Also enabled by fdec.
A warning that the lower bound is being used for a mission dimension
is output unless suppressed by using -Wno-missing-index.
This is... seriously problemati
Hi all,
Similar to a patch I committed a while ago for Cygwin, the attached
patch allows it to pass on the mingw version of gfortran.
It is trivial.
Ok for trunk?
Regards,
Jerrydiff --git a/gcc/testsuite/gfortran.dg/bind_c_array_params_2.f90 b/gcc/testsuite/gfortran.dg/bind_c_array_params_2.f9
Attached patch fixes this problem by allowing the namespace pointer to
be set correctly regardless of error condition.
Regression tested on x86_64_linux_gnu.
OK for trunk and backports?
Regards,
Jerry
Author: Jerry DeLisle
Date: Sat Jan 28 20:00:34 2023 -0800
ICE in
501 - 561 of 561 matches
Mail list logo
