This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/84141] [8 regression] Internal error: type_name(): Bad type


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141

--- Comment #23 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Everybody,

I just got in from the lab.. Obviously, I will not be working on this
problem tonight!

I suspect that fact that I have had to pick out allocatable components
for special treatment is the smoking gun. I will be giving the large
chunk of specialised code devoted to allocatable components in
trans-array.c a good looking over tomorrow. Somewhere, a perfectly
good dtype is being overwirtten with zeros....

Paul


On 1 February 2018 at 22:23, juergen.reuter at desy dot de
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
>
> --- Comment #22 from Jürgen Reuter <juergen.reuter at desy dot de> ---
> I'm actually running our code right now. It fixes _almost all_ of our unit and
> functional tests. There is still one failing unit test and at least one failing
> functional test. Still waiting for the full results. Will try to add a
> reproducer for the test. For the unit test that is straightforward, for the
> functional test maybe not so much.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]