Related articles |
---|
Assembling span-dependent instructions anton@mips.complang.tuwien.ac.at (2022-07-27) |
Re: Assembling span-dependent instructions 480-992-1380@kylheku.com (Kaz Kylheku) (2022-07-27) |
Re: Assembling span-dependent instructions anton@mips.complang.tuwien.ac.at (2022-07-28) |
Re: Assembling span-dependent instructions antispam@math.uni.wroc.pl (2022-07-28) |
Re: Assembling span-dependent instructions gah4@u.washington.edu (gah4) (2022-07-29) |
Re: Assembling span-dependent instructions 480-992-1380@kylheku.com (Kaz Kylheku) (2022-07-29) |
From: | Kaz Kylheku <480-992-1380@kylheku.com> |
Newsgroups: | comp.compilers,comp.arch |
Date: | Wed, 27 Jul 2022 22:52:40 -0000 (UTC) |
Organization: | A noiseless patient Spider |
References: | 22-07-049 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="7304"; mail-complaints-to="abuse@iecc.com" |
Keywords: | code, question |
Posted-Date: | 27 Jul 2022 19:00:36 EDT |
On 2022-07-27, Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
> However, one can also construct cases where making the code larger can
> reduce the minimum size of the immediate operand, e.g.:
>
> foo:
> movl foo+133-bar(%rdi),%eax
> bar:
That's weird; what is accessed this way, relative to the code,
and does it occur in compiler output?
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Return to the
comp.compilers page.
Search the
comp.compilers archives again.