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: Recent change to mips_output_move


> 
> As I understand it, .set nomacro only warns about multi-instruction
> macros, not single-instruction ones.  We've been using move, li and
> dli in delay slots for a long time.
> 

Pretty sure I was getting a warning about move. I'll double check later
though.

> In case it's any reassurance: for the last few months, I've been
> testing with a version of gas in which all .set nomacro warnings
> are hard errors.  I haven't seen it cause any problems.
> 
> > (Really should commit move_register to using or though...)
> 
> Why's that?
> 

So that we're not getting unexpected sign extends on some platforms and
not on others (bcm1250). This way, we're just moving a value, nothing
more.

-eric

-- 
Eric Christopher <echristo@redhat.com>


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