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: preprocessor: % as args to #defines

From: Geoff Keating <geoffk at geoffk dot org>
To: Ian Lance Taylor <ian at wasabisystems dot com>
Cc: Syd Polk <spolk at apple dot com>, corsepiu at faw dot uni-ulm dot de (Ralf Corsepius), gcc at gcc dot gnu dot org (GCC List), Zack Weinberg <zack at codesourcery dot com>, Joern Rennecke <joern dot rennecke at superh dot com>
Date: 29 Jan 2004 15:31:52 -0800
Subject: Re: preprocessor: % as args to #defines
References: <200401291844.i0TIiDT05165@linsvr1.uk.superh.com><87u12eh9kj.fsf@egil.codesourcery.com><C381627E-528C-11D8-8CEA-0003931B8A28@apple.com><AD78EB36-528F-11D8-9D26-000393A6D2F2@physics.uc.edu><m3y8rq1rsi.fsf@gossamer.airs.com>

Ian Lance Taylor <ian@wasabisystems.com> writes:

> While acknowledging that inline assembler is a fertile source of
> problems, I would say that gcc's support for inline assembler is one
> of the main reasons that gcc is useful in compiling for embedded
> systems and kernels.  It permits scheduling of assembler code,

I'm sure you meant another word here, not 'scheduling'.  One of the
best reasons not to use inline asm is that it can't be scheduled.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

Follow-Ups:
- Re: preprocessor: % as args to #defines
  - From: Ian Lance Taylor

References:
- Re: preprocessor: % as args to #defines
  - From: Joern Rennecke
- Re: preprocessor: % as args to #defines
  - From: Zack Weinberg
- Re: preprocessor: % as args to #defines
  - From: Syd Polk
- Re: preprocessor: % as args to #defines
  - From: Andrew Pinski
- Re: preprocessor: % as args to #defines
  - From: Ian Lance Taylor

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