This is the mail archive of the gcc-patches@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: [patch] basic-block.h: Speed up FOR_EACH_EDGE.

From: Kazu Hirata <kazu at cs dot umass dot edu>
To: rth at redhat dot com
Cc: gcc-patches at gcc dot gnu dot org
Date: Mon, 07 Mar 2005 16:02:36 -0500 (EST)
Subject: Re: [patch] basic-block.h: Speed up FOR_EACH_EDGE.
References: <20050301.210353.88490961.kazu@cs.umass.edu><20050307205810.GG26294@redhat.com>

Hi Richard,

> As opposed to (i < length ? e = EDGE_I (blah, i), 1 : 0)?
> Kinda gross, I know, but not horrible for burying in macros.
> I suppose it doesn't matter.

Ah, I forgot about a compound expression.  Some users of FOR_EACH_EDGE
expects e == NULL after the loops, so the condition should look
something like

  (i < length ? e = EDGE_I (blah, i), 1 : e = NULL, 0)

Kazu Hirata

Follow-Ups:
- Re: [patch] basic-block.h: Speed up FOR_EACH_EDGE.
  - From: Andreas Schwab

References:
- [patch] basic-block.h: Speed up FOR_EACH_EDGE.
  - From: Kazu Hirata
- Re: [patch] basic-block.h: Speed up FOR_EACH_EDGE.
  - From: Richard Henderson

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