From: Alan Modra <amodra@gmail.com>
To: dgisselq@ieee.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Missing TO_ADDR
Date: Fri, 08 Apr 2016 05:16:00 -0000 [thread overview]
Message-ID: <20160408051505.GQ18129@bubble.grove.modra.org> (raw)
In-Reply-To: <1459521728.9097.239.camel@jericho>
On Fri, Apr 01, 2016 at 10:42:08AM -0400, Dan wrote:
> Alan,
>
> Sorry, I'm still kind of new to the whole idea of posting patches. Will
> this work better?
>
> 2016-04-01 Dan Gisselquist <dgisselq@ieee.org>
>
> * ld/ldlang.c: Updated minfo lines so that map file sizes are
> given in the target machines address units.
> * ld/ldlang.c: Fixed three other references to section sizes
> that didn't go through the size in octets to target address
> units translation
>
> I used diff -Naur -up this time ...
Thanks, but..
Hunk #1 FAILED at 1886.
Hunk #2 succeeded at 4001 (offset -1 lines).
Hunk #3 succeeded at 4311 (offset -1 lines).
Hunk #4 succeeded at 4356 (offset -1 lines).
Hunk #5 succeeded at 4389 (offset -1 lines).
Hunk #6 FAILED at 5069.
Hunk #7 FAILED at 5086.
3 out of 7 hunks FAILED -- saving rejects to file ld/ldlang.c.rej
..so I put it aside until I wasn't quite so busy. The rejects turned
out to be due to me already committing those changes. Here's what I
committed for you, and the style of changelog we use around here.
2016-04-08 Dan Gisselquist <dgisselq@ieee.org>
* ldlang.c (print_output_section_statement): Show minfo size
in target machine address units.
(print_reloc_statement): Likewise.
(print_padding_statement): Likewise.
(print_data_statement): Likewise. Ensure minimum print_dot
increment of one address unit.
diff --git a/ld/ldlang.c b/ld/ldlang.c
index 9fca810..5fbea3f 100644
--- a/ld/ldlang.c
+++ b/ld/ldlang.c
@@ -4001,7 +4001,7 @@ print_output_section_statement
++len;
}
- minfo ("0x%V %W", section->vma, section->size);
+ minfo ("0x%V %W", section->vma, TO_ADDR (section->size));
if (section->vma != section->lma)
minfo (_(" load address 0x%V"), section->lma);
@@ -4311,7 +4311,9 @@ print_data_statement (lang_data_statement_type *data)
break;
}
- minfo ("0x%V %W %s 0x%v", addr, size, name, data->value);
+ if (size < TO_SIZE ((unsigned) 1))
+ size = TO_SIZE ((unsigned) 1);
+ minfo ("0x%V %W %s 0x%v", addr, TO_ADDR (size), name, data->value);
if (data->exp->type.node_class != etree_value)
{
@@ -4354,7 +4356,7 @@ print_reloc_statement (lang_reloc_statement_type *reloc)
size = bfd_get_reloc_size (reloc->howto);
- minfo ("0x%V %W RELOC %s ", addr, size, reloc->howto->name);
+ minfo ("0x%V %W RELOC %s ", addr, TO_ADDR (size), reloc->howto->name);
if (reloc->name != NULL)
minfo ("%s+", reloc->name);
@@ -4387,7 +4389,7 @@ print_padding_statement (lang_padding_statement_type *s)
addr = s->output_offset;
if (s->output_section != NULL)
addr += s->output_section->vma;
- minfo ("0x%V %W ", addr, (bfd_vma) s->size);
+ minfo ("0x%V %W ", addr, TO_ADDR (s->size));
if (s->fill->size != 0)
{
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2016-04-08 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:32 Alan Modra
2016-03-30 12:08 ` Dan
[not found] ` <1459339484.9097.134.camel@jericho>
2016-03-31 7:40 ` Alan Modra
2016-03-31 11:13 ` Dan
2016-04-01 1:28 ` Alan Modra
2016-03-31 16:03 ` Dan
2016-04-01 1:31 ` Alan Modra
2016-04-01 14:42 ` [PATCH] " Dan
2016-04-08 5:16 ` Alan Modra [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=20160408051505.GQ18129@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=dgisselq@ieee.org \
/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).