From: Paul Brook <paul@codesourcery.com>
To: "S. Bosscher" <S.Bosscher@student.tudelft.nl>,
"'toon@moene.indiv.nluug.nl'" <toon@moene.indiv.nluug.nl>,
"'paul@codesourcery.com'" <paul@codesourcery.com>
Cc: "'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>
Subject: Re:
Date: Sun, 07 Dec 2003 14:17:00 -0000 [thread overview]
Message-ID: <200312071417.05331.paul@codesourcery.com> (raw)
In-Reply-To: <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
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)
Paul
next parent reply other threads:[~2003-12-07 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4195D82C2DB1D211B9910008C7C9B06F01F373E0@lr0nt3.lr.tudelft.nl>
2003-12-07 14:17 ` Paul Brook [this message]
2003-12-08 3:53 ` Re:Updating the TO DO list Feng Wang
2007-03-27 13:13 Paul Richard Thomas
[not found] <8C94B5ACA298987-8B4-8502@WEBMAIL-DB13.sysops.aol.com>
2007-04-12 21:00 ` Re: FX Coudert
2007-07-06 6:27 Re: Tobias Burnus
2007-07-06 8:17 ` Re: Lee Millward
2013-03-12 9:22 Re: DavidLNewton
2013-03-13 5:51 Re: DavidLNewton
2020-07-26 4:49 Damian Rouson
2020-07-26 8:55 ` Arjen Markus
2021-03-10 18:34 mscfd
2021-03-11 7:48 ` Richard Biener
2023-08-22 13:06 Mamadou Diop
2023-08-23 8:19 ` Arjen Markus
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=200312071417.05331.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=S.Bosscher@student.tudelft.nl \
--cc=fortran@gcc.gnu.org \
--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).