public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Dewar <dewar@gnat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Geert Bosch <bosch@gnat.com>,
	 Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Question/proposal for USE_MAPPED_LOCATION and Ada
Date: Wed, 06 Oct 2004 23:04:00 -0000	[thread overview]
Message-ID: <41647306.5040008@gnat.com> (raw)
In-Reply-To: <200410062337.55110.stevenb@suse.de>

Steven Bosscher wrote:

> I don't think having your own location representation is a waste of
> space and time.  Zack likes clean, I'm more pragmatic: It's a design
> decision.

One thing to be aware of in the Ada case is the requirement for
properly tracking the distinction between a generic template and
its instantiations, to all depths of instantiation. In the GNAT
front end, a 32-bit source location is sufficient to record both
the source location in the generic template and the source location
of all instantiations. This is quite important for getting good
error message placement. Source location here = line/column.
> 
> In the Fortran case, the question is:  Does GCC provide adequate
> language independent diagnostics machinery? (A: apparently yes, and
> with a little luck we'll even get column information back!).
> In your case, the question is: Do you want our front end to depend on
> linemap.[ch] outside gigi?  If not, then implement your own location
> representation, translate your representation to that of GCC, accept
> the space and time penalty, and be done with it.

It's probably not that big a penalty I would guess, though, as above,
I would guess this is a "lossy" translation, and that the gcc messages
won't know about instantiations.

  reply	other threads:[~2004-10-06 22:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 21:07 Richard Kenner
2004-10-06 22:03 ` Geert Bosch
2004-10-06 22:21   ` Steven Bosscher
2004-10-06 23:04     ` Robert Dewar [this message]
2004-10-06 23:09       ` Joe Buck
2004-10-06 23:16         ` Robert Dewar
2004-10-06 23:25           ` Steven Bosscher
2004-10-06 23:30             ` Robert Dewar
2004-10-07  2:31               ` James A. Morrison
2004-10-07  6:24                 ` Robert Dewar
2004-10-06 23:26 Richard Kenner
2004-10-07 11:21 ` Giovanni Bajo
2004-10-07 15:42 Richard Kenner
2004-10-07 16:01 ` Giovanni Bajo
2004-10-07 18:28   ` Robert Dewar

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=41647306.5040008@gnat.com \
    --to=dewar@gnat.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=stevenb@suse.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).