From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb build on 32-bit hosts w/ --enable-64-bit-bfd
Date: Tue, 04 Dec 2018 18:59:00 -0000 [thread overview]
Message-ID: <222885d8-9f9f-7808-3ee2-25043f95171b@ericsson.com> (raw)
In-Reply-To: <20181204181650.18188-1-palves@redhat.com>
On 2018-12-04 1:16 p.m., Pedro Alves wrote:
> Building for x86_64/-m32 with --enable-64-bit-bfd, compilation fails
> with:
>
> src/gdb/dwarf2read.c: In instantiation of ‘gdb::array_view<const unsigned char> get_gdb_index_contents_from_section(objfile*, T*) [with T = dwarf2_per_objfile]’:
> src/gdb/dwarf2read.c:6266:54: required from here
> src/gdb/dwarf2read.c:6192:37: error: narrowing conversion of ‘section->dwarf2_section_info::size’ from ‘bfd_size_type {aka long long unsigned int}’ to ‘size_t {aka unsigned int}’ inside { } [-Werror=narrowing]
> return {section->buffer, section->size};
> ~~~~~~~~~^~~~
>
> This fixes it.
Woops, thanks, LGTM.
Simon
prev parent reply other threads:[~2018-12-04 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:16 Pedro Alves
2018-12-04 18:59 ` Simon Marchi [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=222885d8-9f9f-7808-3ee2-25043f95171b@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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