From: Paul Koning <pkoning@equallogic.com>
To: drow@mvista.com
Cc: echristo@redhat.com, wilson@redhat.com, gcc@gcc.gnu.org,
binutils@sources.redhat.com
Subject: Re: MIPS gas relaxation still doesn't work
Date: Wed, 16 Oct 2002 07:53:00 -0000 [thread overview]
Message-ID: <15789.28967.404333.148432@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <20021015210626.GA7254@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
Daniel> On Tue, Oct 15, 2002 at 01:56:47PM -0700, Eric Christopher
Daniel> wrote:
>> > While I agree with you in theory, how would GCC handle
>> user-written > asm("") blocks without an assemble-time jump
>> relaxation of some sort?
>> >
>>
>> Treat them as regions that cannot be scheduled across I believe.
Daniel> No, I mean the problem that Maciej raised: how can we even
Daniel> pretend to know their length? They're a black box; we don't
Daniel> really want to assume that long jumps are necessary over one,
Daniel> but we don't know how big they are.
If you write them with nomacro in effect, you can... Doesn't gcc use
the rule that the length of an asm is the length attribute defined in
the md file, multiplied by the number of statements in the asm string?
Actually, even with macros that works if the md file specifies the
longest macro expansion as its length, but that's rather pessimistic.
paul
next prev parent reply other threads:[~2002-10-16 14:01 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021012113423.A27894@lucon.org>
[not found] ` <20021013145423.A10174@lucon.org>
2002-10-14 9:23 ` H. J. Lu
2002-10-14 9:35 ` Richard Sandiford
2002-10-14 9:37 ` H. J. Lu
2002-10-14 10:04 ` Richard Sandiford
2002-10-14 10:43 ` H. J. Lu
2002-10-14 10:50 ` David S. Miller
2002-10-14 10:53 ` H. J. Lu
2002-10-14 11:13 ` Alexandre Oliva
2002-10-14 11:21 ` H. J. Lu
2002-10-14 12:28 ` Alexandre Oliva
2002-10-14 12:37 ` H. J. Lu
2002-10-14 12:58 ` Alexandre Oliva
2002-10-14 13:00 ` H. J. Lu
2002-10-14 13:08 ` David S. Miller
2002-10-14 13:23 ` H. J. Lu
2002-10-14 14:04 ` David S. Miller
2002-10-14 14:14 ` H. J. Lu
2002-10-14 14:17 ` Alexandre Oliva
2002-10-14 14:18 ` H. J. Lu
2002-10-14 15:37 ` Alexandre Oliva
2002-10-14 15:40 ` H. J. Lu
2002-10-15 1:08 ` Alexandre Oliva
2002-10-15 2:53 ` Dominic Sweetman
2002-10-15 8:12 ` Alexandre Oliva
2002-10-15 14:18 ` Jim Wilson
2002-10-15 13:27 ` Maciej W. Rozycki
2002-10-15 16:37 ` Jim Wilson
2002-10-16 6:39 ` Maciej W. Rozycki
2002-10-16 10:38 ` Jim Wilson
2002-10-15 18:40 ` Alexandre Oliva
2002-10-16 7:01 ` Maciej W. Rozycki
2002-10-16 7:47 ` Alexandre Oliva
2002-10-16 8:06 ` Maciej W. Rozycki
2002-10-14 17:02 ` Eric Christopher
2002-10-15 1:15 ` Alexandre Oliva
2002-10-14 14:44 ` Michael Matz
2002-10-15 13:28 ` Jim Wilson
2002-10-15 13:45 ` Paul Koning
2002-10-15 14:32 ` Maciej W. Rozycki
2002-10-15 15:33 ` Alexandre Oliva
2002-10-16 5:32 ` Maciej W. Rozycki
2002-10-15 14:00 ` Daniel Jacobowitz
2002-10-15 14:56 ` Eric Christopher
2002-10-15 15:05 ` Daniel Jacobowitz
2002-10-16 7:53 ` Paul Koning [this message]
2002-10-16 8:11 ` Maciej W. Rozycki
2002-10-15 15:23 ` Jim Wilson
2002-10-16 5:38 ` Maciej W. Rozycki
2002-10-16 10:37 ` Jim Wilson
2002-10-16 11:04 ` Maciej W. Rozycki
2002-10-15 16:54 ` Richard Henderson
2002-10-14 9:40 ` Alexandre Oliva
2002-10-14 9:44 ` H. J. Lu
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=15789.28967.404333.148432@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=wilson@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).