MIPS assembler branch relaxations

Eric Christopher echristo@redhat.com
Sat Sep 14 21:33:00 GMT 2002


> > > More importantly, because the performance of this is not important or
> > > particularly good, it's important to avoid it.  When will it trigger? 
> > > Does it require -relax?  [Not sure.] Does it happen inside .set
> > > nomacro? [I think so - should it?  I'd say not!] I think there should
> > > be a command-line option to disable this, and/or warn about it.  Most
> > > out-of-range branches represent bugs in GCC's calculations of
> > > instruction lengths.  I know there are some in 3.2, because I've run
> > > into them.  I don't know if they're fixed in HEAD, and if this goes in
> > > I may never find out.
> > > 
> > 
> > 1) None of the other relaxations require a command line.
> > 2) always.
> > 3) no
> > 4) shouldn't - good catch.
> > 5) not always, macros are partially to blame.
> > 6) you and i had a conversation about this very thing yesterday :)
> > 
> > Anyhow, if 4 is I'm pretty happy with it going in.
> 
> Er... um... could I get that said again with more words?  I have no
> idea what you just said.
> 

How about "if relaxation doesn't happen within set nomacro" i'm pretty
happy with it going in. Or did you want all of them expanded? They were
just answers to your questions.

-eric

-- 
Yuppies wear socks.



More information about the Binutils mailing list