From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Henderson <rth@redhat.com>,
Daniel Jacobowitz <drow@mvista.com>,
binutils@sources.redhat.com, echristo@redhat.com
Subject: Re: MIPS assembler branch relaxations
Date: Tue, 17 Sep 2002 00:38:00 -0000 [thread overview]
Message-ID: <20020917070909.GD20322@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <orfzw9rxv8.fsf@free.redhat.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
> On Sep 16, 2002, Richard Henderson <rth@redhat.com> wrote:
>
> >> Does the linker refrain from doing relaxations on machine code
> >> generated from opcodes assembled while .set nomacro was in effect?
>
> > What linker relaxations?
>
> coff-mips does them for embedded pic. I thought we did more of those,
> given the references to linker relaxations in comments in the
> assembler.
>
> Ok, I'm now convinced not doing such relaxations under certain
> conditions is the way to go. But what are the exact conditions?
> nomacro (as suggested),
Always, as it should prevent expansions.
> noat (to avoid clobbering $at in the expanded
> sequences)
Only if $at is actually used. AFAICS this is the PIC case.
> and no gp (to avoid depending on uninitialized values)?
AFAICS $gp is only used for PIC, where it must be defined anyway.
Btw, your patch uses explicit binary patterns to create insns, is it
actually impossible to use mips_ip()/append_insn() instead?
Thiemo
next prev parent reply other threads:[~2002-09-17 7:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 4:49 Alexandre Oliva
2002-09-14 14:28 ` Daniel Jacobowitz
2002-09-14 14:46 ` Eric Christopher
2002-09-14 21:33 ` Daniel Jacobowitz
2002-09-14 21:33 ` Eric Christopher
2002-09-14 15:00 ` Paul Koning
2002-09-14 16:35 ` Daniel Jacobowitz
2002-09-14 18:43 ` Paul Koning
2002-09-14 21:39 ` Thiemo Seufer
2002-09-14 22:18 ` Alexandre Oliva
2002-09-15 2:25 ` Thiemo Seufer
2002-09-15 3:38 ` Alexandre Oliva
2002-09-15 0:49 ` Alexandre Oliva
2002-09-15 9:15 ` Daniel Jacobowitz
2002-09-16 11:56 ` Richard Henderson
2002-09-17 0:09 ` Alexandre Oliva
2002-09-17 0:26 ` Richard Henderson
2002-09-17 0:38 ` Thiemo Seufer [this message]
2002-10-09 16:51 ` Alexandre Oliva
2002-10-09 16:54 ` Alexandre Oliva
2002-10-09 17:17 ` H. J. Lu
2002-10-11 13:08 ` Eric Christopher
2002-09-14 14:39 ` H. J. Lu
2002-09-14 23:12 ` Alexandre Oliva
2002-09-15 9:13 ` H. J. Lu
2002-09-15 15:32 ` Eric Christopher
2002-09-15 16:53 ` H. J. Lu
2002-09-15 1:00 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020917070909.GD20322@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=echristo@redhat.com \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).