From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: fortran regression [was Re: Results for egcs-971207 on m68k-next-nextstep3]
Date: Thu, 11 Dec 1997 11:14:00 -0000 [thread overview]
Message-ID: <rzqvhwvzoaw.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <11472.881801160@hurl.cygnus.com>
>>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
Jeffrey> It is most likely the gcc2 brought over in the last merge
Jeffrey> which try and flag arrays that are too big
Jeffrey> (compile/961203-1.c bug).
Ah. Doubtless.
Jeffrey> We need to figure out how to make fortran work with that
Jeffrey> code, either by fixing the gcc2 changes or the fortran front
Jeffrey> end.
AFAIR the front end is somewhat hamstrung (perhaps depending on
exactly what the issue is) and there have been long-standing problems,
especially with the debugging info generated leading to gdb crashes
trying to assumed-size arrays (which used to appear with huge or
negative dimensions). There's an essay on this area in f/com.c
(ffecom_sym_transform_), at least I think it's relevant.
I think Fortran isn't really usable until this is resolved somehow
because that construct is very common. I doubt I can be much help
other than maybe explaining the fortran issues if a wizard is able to
look into it.
next prev parent reply other threads:[~1997-12-11 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 7:08 Results for egcs-971207 on m68k-next-nextstep3 Toon Moene
1997-12-10 13:36 ` fortran regression [was Re: Results for egcs-971207 on m68k-next-nextstep3] Dave Love
1997-12-10 16:43 ` Jeffrey A Law
1997-12-11 11:14 ` Dave Love [this message]
1997-12-11 16:33 ` Craig Burley
1997-12-12 10:18 ` Dave Love
1997-12-12 18:04 ` Craig Burley
[not found] ` <rzqd8j2zb5m.fsf.cygnus.egcs@djlvig.dl.ac.uk>
1997-12-12 15:46 ` Jason Merrill
1997-12-13 10:44 ` Dave Love
1997-12-15 23:18 ` g77 assumed array patch [was: fortran regression] Richard Henderson
1997-12-18 23:19 ` Jeffrey A Law
1997-12-19 12:37 ` Dave Love
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=rzqvhwvzoaw.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
/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).