public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: Alan Modra <amodra@gmail.com>,
	Tristan Gingold <gingold@adacore.com>,	<binutils@sourceware.org>
Subject: Re: [rfc] new bfd hook: additional link map text
Date: Tue, 03 Jun 2014 15:43:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1406031638460.6087@tp.orcam.me.uk> (raw)
In-Reply-To: <201405100233.s4A2XCOR030016@greed.delorie.com>

On Sat, 10 May 2014, DJ Delorie wrote:

> Here's the current patch, without the debugs, with elf32-rx.h, and
> without the old bfd hook.
> 
> In case you're wondering, the purpose for all this is to have better
> support for auto-generated interrupt vector tables.  The compiler sets
> up all the hooks, the bfd pass stitches the tables together, and this
> new linker map hook dumps the generated table info to the map file.
> 
> 	* bfd/elf32-rx.c (get_symbol_value_maybe): New.
> 	(rx_elf_relocate_section): If we find a reloc against
> 	$tableentry$default$<name>, redirect it to the appropriate
> 	$tableentry$<n>$.
> 	(RX_Table_Info): New.
> 	(rx_table_find): New.  Check all tables and SEC_KEEP all sections
> 	with table parts in them.
> 	(rx_check_directives): New.
> 	(rx_table_map_2): New.
> 	(rx_table_map): New.
> 	(rx_additional_link_map_text): New.  Called to dump tables to the
> 	map file.
> 	* bfd/elf32-rx.h: New.

 This change doesn't build with the i686-linux-gnu host, mips-linux-gnu 
target, --enable-targets=all:

cc1: warnings being treated as errors
.../bfd/elf32-rx.c: In function 'rx_table_map':
.../bfd/elf32-rx.c:3871: error: format '%08lx' expects type 'long unsigned int', but argument 5 has type 'bfd_vma'
.../bfd/elf32-rx.c:3876: error: format '%08lx' expects type 'long unsigned int', but argument 4 has type 'bfd_vma'
.../bfd/elf32-rx.c:3879: error: format '%08lx' expects type 'long unsigned int', but argument 3 has type 'bfd_vma'
.../bfd/elf32-rx.c:3895: error: format '%08lx' expects type 'long unsigned int', but argument 3 has type 'bfd_vma'
.../bfd/elf32-rx.c:3910: error: format '%08lx' expects type 'long unsigned int', but argument 3 has type 'bfd_vma'
.../bfd/elf32-rx.c:3915: error: format '%08lx' expects type 'long unsigned int', but argument 3 has type 'bfd_vma'
make[4]: *** [elf32-rx.lo] Error 1

  Maciej

  parent reply	other threads:[~2014-06-03 15:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  2:14 DJ Delorie
2014-04-11  7:10 ` Tristan Gingold
2014-04-22 20:55   ` DJ Delorie
2014-05-06 15:15     ` DJ Delorie
2014-05-07  3:02       ` Alan Modra
2014-05-07  3:13         ` DJ Delorie
2014-05-10  2:33         ` DJ Delorie
2014-05-27 15:53           ` DJ Delorie
2014-05-27 16:20             ` Nicholas Clifton
2014-05-27 21:16               ` DJ Delorie
2014-05-28 13:13                 ` Alan Modra
2014-05-27 22:04           ` Breakage with "[rfc] new bfd hook: additional link map text" Hans-Peter Nilsson
2014-05-27 23:06             ` DJ Delorie
2014-06-03 15:43           ` Maciej W. Rozycki [this message]
2014-06-03 15:58             ` [rfc] new bfd hook: additional link map text DJ Delorie
2014-06-03 16:20               ` Maciej W. Rozycki
2014-06-03 16:25                 ` DJ Delorie
2014-06-03 20:25             ` DJ Delorie
2014-06-04 11:56               ` Maciej W. Rozycki

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=alpine.DEB.1.10.1406031638460.6087@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --cc=gingold@adacore.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).