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: gcc-4.3.0/ppc32 inline assembly produces bad code

From: Andreas Schwab <schwab at suse dot de>
To: Till Straumann <strauman at slac dot stanford dot edu>
Cc: gcc at gcc dot gnu dot org, RTEMS List <rtems-users at rtems dot com>
Date: Thu, 27 Mar 2008 10:59:33 +0100
Subject: Re: gcc-4.3.0/ppc32 inline assembly produces bad code
References: <47EA78E1.2040100@slac.stanford.edu> <20080326164039.GA6747@caradoc.them.org> <47EAA5EF.2030901@slac.stanford.edu>

Till Straumann <strauman@slac.stanford.edu> writes:

> In any case, bad code is also produced by gcc-4.3.0 if I omit the
> memory output operand and use an example that comes pretty
> close to what is in the gcc info page (example illustrating
> a memory input in the 'extended asm' section):

Would you mind creating a bug report at <http://gcc.gnu.org/bugzilla>?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- gcc-4.3.0/ppc32 inline assembly produces bad code
  - From: Till Straumann
- Re: gcc-4.3.0/ppc32 inline assembly produces bad code
  - From: Daniel Jacobowitz
- Re: gcc-4.3.0/ppc32 inline assembly produces bad code
  - From: Till Straumann

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