From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24328] [dwz] Combining files with different pointer sizes switches off multifile mode
Date: Mon, 15 Mar 2021 09:16:03 +0000 [thread overview]
Message-ID: <bug-24328-11298-6jkL7Jq8Zp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24328-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24328
Martin Liska <mliska at suse dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mliska at suse dot cz
--- Comment #3 from Martin Liska <mliska at suse dot cz> ---
Hi Tom.
I would like to remind this issue. I believe we can benefit from it as there
are packages that combine different pointer sizes:
firescope.log:[ 50s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
gcc10.log:[10958s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
gcc7.log:[ 5609s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
gcc9.log:[ 3210s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
kernel-debug.log:[12564s] dwz: Multi-file optimization not allowed for
different pointer sizes or endianity
kernel-default.log:[ 2057s] dwz: Multi-file optimization not allowed for
different pointer sizes or endianity
kernel-kvmsmall.log:[ 1163s] dwz: Multi-file optimization not allowed for
different pointer sizes or endianity
kernel-vanilla.log:[ 1432s] dwz: Multi-file optimization not allowed for
different pointer sizes or endianity
lmms.log:[ 1200s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
rr.log:[ 112s] dwz: Multi-file optimization not allowed for different pointer
sizes or endianity
valgrind.log:[ 736s] dwz: Multi-file optimization not allowed for different
pointer sizes or endianity
About multifile mode: I would print warning for a situation where just a single
shared library (or executable)
is provided for a pointer width.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-15 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24328] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24328] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2021-03-15 9:16 ` mliska at suse dot cz [this message]
2021-03-15 10:08 ` rguenth at gcc dot gnu.org
2021-03-15 10:12 ` jakub at redhat dot com
2021-03-15 10:18 ` rguenth at gcc dot gnu.org
2021-03-15 10:25 ` vries at gcc dot gnu.org
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=bug-24328-11298-6jkL7Jq8Zp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.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).