From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Neal Frager <neal.frager@amd.com>, binutils@sourceware.org
Cc: ibai.erkiaga-elorza@amd.com, nagaraju.mekala@amd.com,
mark.hatle@amd.com, sadanand.mutyala@amd.com,
appa.rao.nali@amd.com, vidhumouli.hunsigida@amd.com,
luca.ceresoli@bootlin.com, nickc@redhat.com
Subject: Re: [PATCH v1 1/1] bfd: microblaze: Fix automated build errors
Date: Sat, 7 Oct 2023 11:56:54 -0700 [thread overview]
Message-ID: <74ce52f1-9554-9968-a653-518ca4c99730@oracle.com> (raw)
In-Reply-To: <20231007071110.401935-1-neal.frager@amd.com>
On 10/7/23 00:11, Neal Frager wrote:
> This patch fixes the following automated build errors:
> https://builder.sourceware.org/buildbot/#/builders/80/builds/2101/steps/4/logs/stdio
> https://builder.sourceware.org/buildbot/#/builders/72/builds/3405/steps/4/logs/stdio
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> bfd/elf32-microblaze.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/bfd/elf32-microblaze.c b/bfd/elf32-microblaze.c
> index a8ced43c08a..96bb63fbd2e 100644
> --- a/bfd/elf32-microblaze.c
> +++ b/bfd/elf32-microblaze.c
> @@ -1986,7 +1986,7 @@ microblaze_elf_relax_section (bfd *abfd,
> /* Validate the in-band val. */
> val = bfd_get_32 (abfd, contents + irel->r_offset);
> if (val != irel->r_addend && ELF32_R_TYPE (irel->r_info) == R_MICROBLAZE_32_NONE) {
> - fprintf(stderr, "%d: CORRUPT relax reloc %x %lx\n", __LINE__, val, irel->r_addend);
> + fprintf(stderr, "%d: CORRUPT relax reloc %x %x\n", __LINE__, val, irel->r_addend);
The type of irel->r_addend is "bfd_vma".
"bfd_vma" can be "unsigned long" or "unsigned int".
Perhaps the correct fix is:
fprintf(stderr, "%d: CORRUPT relax reloc %x %lx\n", __LINE__, val, (unsigned long) irel->r_addend);
or
fprintf(stderr, "%d: CORRUPT relax reloc %x %llx\n", __LINE__, val, (unsigned long long) irel->r_addend);
next prev parent reply other threads:[~2023-10-07 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 7:11 Neal Frager
2023-10-07 18:56 ` Vladimir Mezentsev [this message]
2023-10-09 6:13 ` Frager, Neal
2023-10-09 16:05 ` Vladimir Mezentsev
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=74ce52f1-9554-9968-a653-518ca4c99730@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=appa.rao.nali@amd.com \
--cc=binutils@sourceware.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=mark.hatle@amd.com \
--cc=nagaraju.mekala@amd.com \
--cc=neal.frager@amd.com \
--cc=nickc@redhat.com \
--cc=sadanand.mutyala@amd.com \
--cc=vidhumouli.hunsigida@amd.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).