From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
FX Coudert <fxcoudert@gmail.com>,
Tobias Burnus <burnus@net-b.de>,
Steve Kargl <sgk@troutmask.apl.washington.edu>,
Janus Weil <janus@gcc.gnu.org>,
Dominique Dhumieres <dominiq@lps.ens.fr>,
Thomas Koenig <tkoenig@netcologne.de>,
Andre Vehreschild <vehre@gmx.de>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: Triage of fortran FE regressions
Date: Wed, 06 Jan 2016 20:18:00 -0000 [thread overview]
Message-ID: <CAGkQGi+fmE5FR+z6WvJRw4ByRSL=0LoiK=7GyOLZpsv9V1LjXA@mail.gmail.com> (raw)
In-Reply-To: <568D6146.4080303@sfr.fr>
Hi Mikael,
I had thought that you might be tied up! Anything that you can do
would be gratefully received.
Cheers
Paul
On 6 January 2016 at 19:47, Mikael Morin <mikael.morin@sfr.fr> wrote:
> Hello Paul,
>
> a status update for the bugs I am associated with.
>
>> Reported in 2013 or before:
>
> [...]
>>
>> 57048 [4.9/5/6 Regression] Handling of C_PTR and C_FUNPTR leads to
>> reject valid
>> Mikael was working on it.
>
> I wasn't even close to a working patch, and have no time for it in the
> foreseeable future.
> [...]
>
>>
>> Reported in 2014:
>
> [...]
>>
>> 60500 [4.9/5/6 Regression] Spurious warning on derived type
>> initialization
>> Mikael diagnosed the problem.
>
> Initialisation is somewhat messy, it is sometimes generated by artificial
> statements during resolution, sometimes done in the translation phase. It's
> easy to fix one end and break the other end (ending up with either
> conflicting initializations or missing ones).
> I haven't really tried to fix this one, basically the initialization code
> that caused the bug should be moved from the resolution phase to the
> translation phase.
> [...]
>>
>> 61831 [4.9/ 5 Regression] runtime error: pointer being freed was
>> not allocated
>> Mikael, is this fixed or not?
>
> The original problem is fixed on trunk as far as I know.
> For the branches the kludge proposed by Dominique (which regresses a memory
> leak PR) could be used. I had planned to strip the boolean argument from
> expr_may_alias_variables and replace Dominique's kludge by a call to
> expr_may_alias_variables as patch for the branches.
> IIRC, it didn't simply pass the testcase, or I had a more complex one that
> failed, and I gave up after an hour or so scratching my head.
>
>>
>> Reported in 2015
>
> [...]
>>
>> 66089 [6 Regression] elemental dependency mishandling when derived
>> types are involved
>> Mikael posted fix.
>
> The fix works as far as I know, but each condition in
> gfc_scalar_elemental_arg_saved_as_reference can potentially lead to the same
> bug and needs auditing.
> [...]
>>
>> 68560 [6 Regression] The test gfortran.dg/shape_8.f90 now fails
>> when compiled with -flto
>> Mikael was on the way to a patch....
>
> The patch has been needing one more fix after one more fix.
>
>
> In general, I have little time to devote to gfortran.
> I can have a look at PR66089 as a start, possibly PR68560 as well, but I
> probably need more time for the other, so don't hold your breath for them.
>
> Mikael
--
The difference between genius and stupidity is; genius has its limits.
Albert Einstein
prev parent reply other threads:[~2016-01-06 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 13:09 Paul Richard Thomas
[not found] ` <264F4394-0CD9-4AB0-88F4-C40A9D00D619@lps.ens.fr>
2016-01-05 13:26 ` Dominique d'Humières
2016-01-05 13:35 ` Andre Vehreschild
2016-01-05 15:35 ` Paul Richard Thomas
2016-01-05 18:28 ` Paul Richard Thomas
2016-01-05 23:28 ` Jerry DeLisle
2016-01-06 18:47 ` Mikael Morin
2016-01-06 20:18 ` Paul Richard Thomas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGkQGi+fmE5FR+z6WvJRw4ByRSL=0LoiK=7GyOLZpsv9V1LjXA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=burnus@net-b.de \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=jakub@redhat.com \
--cc=janus@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=sgk@troutmask.apl.washington.edu \
--cc=tkoenig@netcologne.de \
--cc=vehre@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).