Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com, jimb@redhat.com
Subject: Re: [RFA] Harvard extensions for cast expressions
Date: Mon, 05 Nov 2001 15:36:00 -0000	[thread overview]
Message-ID: <3BF32545.F600CB9C@cygnus.com> (raw)
In-Reply-To: <3BF30D0A.3000102@cygnus.com>

Andrew Cagney wrote:
> 
> > This is a re-submission, with suggested clean-ups, of an extension
> > posted in September to allow cast expressions to include a modifier
> > which designates an address space (for now, either "code" or "data").
> >
> > Future work may be expected to extend this so that address spaces
> > can be added dynamically at runtime.
> >
> > 2001-09-28  Michael Snyder  <msnyder@redhat.com>
> > Add address space identifiers to expression language for types.
> >       * c-exp.y (space_identifier, cv_with_space_id,
> >       const_or_volatile_or_space_identifier_noopt,
> >       const_or_volatile_or_space_identifier): New terminals.
> >       (ptype): Accept const_or_volatile_or_space_identifier.
> >       (typebase): Accept const_or_volatile_or_space_identifier.
> >       * c-typeprint.c (c_type_print_cv_qualifier): Rename to
> >       c_type_print_modifier.  Handle address space modified types.
> >       * gdbtypes.h (TYPE_FLAG_CODE_SPACE, TYPE_FLAG_DATA_SPACE):
> >       New type flags.
> >       (struct type): Add new field as_type for addr-space qualified types.
> >       (TYPE_AS_TYPE): New macro, retrieves the chain of types that are
> >       identical to this one except for address-space qualification.
> >       * gdbtypes.c (alloc_type): Initialize new field 'as_type'.
> >       (address_space_name_to_int): New function.
> >       (address_space_int_to_name): New function.
> >       (make_type_with_address_space): New function.
> >       (make_cv_type): Handle as_type field of new struct type object.
> >       * parse.c (check_type_stack_depth): New function.
> >       (push_type_address_space): New function.
> >       (follow_types): Handle types with address-space qualifier.
> >       * parser-defs.h (enum type_pieces): Add enum tp_space_identifier.
> >
> >
> Yes, ok.
> Andrew

Committed.


      reply	other threads:[~2001-11-15  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 13:26 Michael Snyder
2001-11-05 15:36 ` Andrew Cagney
2001-11-05 15:36   ` Michael Snyder [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=3BF32545.F600CB9C@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.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