This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: decl_conflicts_with_clobbers_p problem
Gunther Nikl <gni at gecko dot de> writes:
|> On Thu, Mar 13, 2003 at 11:06:11AM +0100, Andreas Schwab wrote:
|> > Gunther Nikl <gni at gecko dot de> writes:
|> >
|> > |> The clobber list contains all registers that can be changed by a system
|> > |> function as defined by the system ABI. In this example the system function
|> > |> expects its argument in register "a1". Thus the value for _n1 is bound to
|> > |> register "a1" and passed as an input to the asm() statement. With GCC 3.3
|> > |> the asm statement is rejected because of overlapping inputs and clobbers :-(
|> > |> For me the asm statememt looks fine because I must pass the argument in
|> > |> register "a1" and its correct that the contents of register "a1" cannot be
|> > |> relied on after the call anymore.
|> > |> Is the example asm statement wrong or is decl_conflicts_with_clobbers_p()
|> > |> wrong?
|> >
|> > Just list _n1 as an output operand.
|>
|> Sorry, but I don't understand that suggestion. Why is that supposed to
|> help?
To tell the compiler that _n1 is an output operand, which in fact it is.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab at suse dot de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."