public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: "S. Bosscher" <S.Bosscher@student.tudelft.nl>,
	"'Geoff Keating '" <geoffk@geoffk.org>,
	"'gcc mailing list '" <gcc@gcc.gnu.org>
Subject: RE: [tree-ssa][ GC, Virtual operands, and GCing between passes
Date: Thu, 11 Dec 2003 15:01:00 -0000	[thread overview]
Message-ID: <1071153258.10274.59.camel@p4> (raw)
In-Reply-To: <1071152867.10274.49.camel@p4>

On Thu, 2003-12-11 at 09:27, Andrew MacLeod wrote:
> On Thu, 2003-12-11 at 09:14, S. Bosscher wrote:
> > > The problem is that gengtype will not allow me to have vevotrs of type

> 
> 
> So that doesn't work for me either.
> 
> I am lothe to use the other patch until it is accepted by someone. OH, I
> see Jim OK'd it. Has it been checked into mainline or the tree-ssa
> branch?
> 

Even with the patch I still get:
./gengtype
warning: structure `java_line' used but not defined
warning: structure `jdeplist_s' used but not defined
warning: structure `java_lexer' used but not defined
warning: structure `ZipDirectory' used but not defined
warning: structure `aterm_list_a' used but not defined
warning: structure `aterm_' used but not defined
/src/tree-ssa/2003-12-10-new/gcc/gcc/tree-ssa-operands.h:30: field
`(*x).def_ops.defs' is pointer to unimplemented type
/src/tree-ssa/2003-12-10-new/gcc/gcc/tree-ssa-operands.h:38: field
`(*x).use_ops.uses' is pointer to unimplemented type

typedef struct def_optype_d GTY(())
{
  unsigned num_defs;
  void * GTY(()) defs;
} def_optype_t;

or
typedef struct def_optype_d GTY(())
{
  unsigned num_defs;
  void * defs;
} def_optype_t;
or
ypedef struct def_optype_d GTY(())
{
  unsigned num_defs;
  void **GTY(()) defs;
} def_optype_t;

etc.



  reply	other threads:[~2003-12-11 14:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 14:27 S. Bosscher
2003-12-11 14:34 ` Andrew MacLeod
2003-12-11 15:01   ` Andrew MacLeod [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09 20:26 Andrew MacLeod
2003-12-09 23:43 ` Geoff Keating
2003-12-10  4:46   ` Andrew MacLeod
2003-12-11 17:01     ` Geoff Keating
2003-12-11 17:17       ` Andrew MacLeod
2003-12-11 21:15         ` Geoff Keating
2003-12-11 23:31           ` Andrew MacLeod
2003-12-15 22:05             ` Richard Henderson
2003-12-15 22:46               ` Andrew MacLeod
2003-12-11 19:30     ` law
2003-12-11 23:13       ` Andrew MacLeod
2003-12-12  0:21         ` law
2003-12-12  3:29           ` Andrew MacLeod
2003-12-12  5:24             ` law
2003-12-12 13:38               ` Andrew MacLeod
2003-12-13  6:52                 ` law
2003-12-11 14:17   ` Andrew MacLeod
2003-12-10  0:03 ` Jan Hubicka
2003-12-10  0:18   ` Andrew MacLeod
2003-12-10  0:38     ` Jan Hubicka
2003-12-11 19:30 ` law

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=1071153258.10274.59.camel@p4 \
    --to=amacleod@redhat.com \
    --cc=S.Bosscher@student.tudelft.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    /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).