From: "Feng Wang" <wf_cs@yahoo.com>
To: Paul Brook <paul@codesourcery.com>,
"S. Bosscher" <S.Bosscher@student.tudelft.nl>,
"'toon@moene.indiv.nluug.nl'" <toon@moene.indiv.nluug.nl>
Cc: "'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>
Subject: Re:Updating the TO DO list.
Date: Mon, 08 Dec 2003 03:53:00 -0000 [thread overview]
Message-ID: <20031208035346.3548.qmail@web15301.mail.bjs.yahoo.com> (raw)
In-Reply-To: <200312071417.05331.paul@codesourcery.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312, Size: 1437 bytes --]
--- Paul Brook <paul@codesourcery.com> µÄÕýÎÄ£º> On Sunday 07 December 2003
1:47 pm, S. Bosscher wrote:
> > > > Implementing ASSIGN probably comes under this category as well.
> > >
> > > This would go into the g77 compatibility department ?
> >
> > Yes.
> >
> > It's also in the top 5 of my TODO list, as you know, since we
> > also need it to be able to compile SPEC ;-)
>
> In that case, you might want to consider not using computed gotos (in the C
> sense) to implement this. I'm of the opinion that it would be better to
> translate assigned gotos into select with normal gotos. All assigned goto
> labels must be within the same program unit as the label. It should be
> fairly easy to build an indexed list of targets, and use the index as the
> assigned value and the consdition for the switch.
>
> I haven't actually done any bechmarks, but I would expect the optimizers to
> translate this into code at least as good as using a [C] computed goto. It
> avoids problems on machines where sizeof (void*) > KIND(0), and allows us
> to take advantage of statements like
> GOTO foo (100, 200)
>
I have implemented ASSIGN, assigned goto and the integer variable can be used
in i/o statements. But it is still at test. ASAP I will give the patch.
> Paul
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
prev parent reply other threads:[~2003-12-08 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
2003-12-07 14:17 ` Paul Brook
2003-12-08 3:53 ` Feng Wang [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=20031208035346.3548.qmail@web15301.mail.bjs.yahoo.com \
--to=wf_cs@yahoo.com \
--cc=S.Bosscher@student.tudelft.nl \
--cc=fortran@gcc.gnu.org \
--cc=paul@codesourcery.com \
--cc=toon@moene.indiv.nluug.nl \
/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).