From: law@redhat.com
To: Alan Modra <amodra@bigpond.net.au>
Cc: Joern Rennecke <amylaar@redhat.com>,
binutils@sources.redhat.com, amylaar@cambridge.redhat.com
Subject: Re: fix for fixup_segment / MD_PCREL_FROM_SECTION
Date: Wed, 29 Aug 2001 08:11:00 -0000 [thread overview]
Message-ID: <16399.999098048@localhost.localdomain> (raw)
In-Reply-To: <20010829150419.G26936@bubble.sa.bigpond.net.au>
In message < 20010829150419.G26936@bubble.sa.bigpond.net.au >you write:
> On Tue, Aug 28, 2001 at 09:07:53PM +0100, Joern Rennecke wrote:
> > be made. On many processors, the base of a PC relative instruction is
> the next
> > instruction, so this macro would return the length of an instruction.
> > + @item TC_MD_PCREL_FROM_SECTION_FIXED
> > + @cindexTC_MD_PCREL_FROM_SECTION_FIXED
> > + You also need to define @code{TC_MD_PCREL_FROM_SECTION_FIXED} to make t
> his
> > + work right, because a large number of old ports papered over a bug in
> > + fixup_segment by making the reverse error in their definition of
> > + @code{MD_PCREL_FROM_SECTION}.
>
> Hmm, alternatively, just modify the doco for MD_PCREL_FROM_SECTION to
> reflect reality. Note also that your patch misses a number of other
> places where MD_PCREL_FROM_SECTION is used.
Ironic -- this is what I suggested to Joern privately when he indicated
that every port which uses MD_PCREL_FROM_SECTION was wrong according
to the documentation.
jeff
prev parent reply other threads:[~2001-08-29 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 13:07 Joern Rennecke
2001-08-28 16:38 ` law
2001-08-28 22:34 ` Alan Modra
2001-08-29 4:09 ` Joern Rennecke
2001-08-29 5:05 ` Alan Modra
2001-08-29 8:11 ` law [this message]
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=16399.999098048@localhost.localdomain \
--to=law@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=amylaar@cambridge.redhat.com \
--cc=amylaar@redhat.com \
--cc=binutils@sources.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).