This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: We're out of tree codes; now what?

From: Diego Novillo <dnovillo at redhat dot com>
To: Steven Bosscher <stevenb dot gcc at gmail dot com>
Cc: Doug Gregor <doug dot gregor at gmail dot com>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, dje at watson dot ibm dot com, gcc at gcc dot gnu dot org, "Sayle, Roger" <roger at eyesopen dot com>
Date: Mon, 19 Mar 2007 11:17:35 -0400
Subject: Re: We're out of tree codes; now what?
References: <doug.gregor@gmail.com> <24b520d20703121113y61cd3911odd9c385ff775dfb9@mail.gmail.com> <200703121835.l2CIZb830240@makai.watson.ibm.com> <571f6b510703121230n73018556g470917c8d9fc6a2a@mail.gmail.com> <24b520d20703121301i6dc3a73fx765b859dabf7e595@mail.gmail.com> <10703122152.AA19282@vlsi1.ultra.nyu.edu> <24b520d20703190641j5cfdfcb0xeaa7a498b909b539@mail.gmail.com> <571f6b510703190714u55b4e5eera5627b9fc6778f0d@mail.gmail.com>

Steven Bosscher wrote on 03/19/07 10:14:

> IMHO this is still the better solution than the subcodes idea.

Agreed.  If the performance hit is not too large, getting a wider tree
code is much simpler to maintain.

References:
- We're out of tree codes; now what?
  - From: Doug Gregor
- Re: We're out of tree codes; now what?
  - From: David Edelsohn
- Re: We're out of tree codes; now what?
  - From: Steven Bosscher
- Re: We're out of tree codes; now what?
  - From: Doug Gregor
- Re: We're out of tree codes; now what?
  - From: Richard Kenner
- Re: We're out of tree codes; now what?
  - From: Doug Gregor
- Re: We're out of tree codes; now what?
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]