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: Mon, 31 Mar 2008 17:47:21 +0200
Subject: Re: gcc-4.3.0/ppc32 inline assembly produces bad code
References: <47EA78E1.2040100@slac.stanford.edu> <jeve33b68u.fsf@sykes.suse.de> <47F105FC.5010908@slac.stanford.edu>

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

>   asm volatile ("lwz %0, 16(%1)":"=r"(val):"b"(base),"m"(*reg_p));

    asm volatile ("lwz%U1%X1 %0, %1":"=r"(val):"m"(*reg_p));

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."

Follow-Ups:
- Re: gcc-4.3.0/ppc32 inline assembly produces bad code
  - From: Till Straumann

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: Andreas Schwab
- 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]