From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24328] New: [dwz] Combining files with different pointer sizes switches off multifile mode
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24328-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24328
Bug ID: 24328
Summary: [dwz] Combining files with different pointer sizes
switches off multifile mode
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
Consider 64-bit and 32-bit hello world executables:
...
$ gcc hello.c -g -m64 -o 1; cp 1 2
$ gcc hello.c -g -m32 -o 3; cp 3 4
...
When running dwz in multifile mode, we get:
...
$ dwz -m 5 1 2 3 4
dwz: Multi-file optimization not allowed for differentpointer sizes or
endianity
$ echo $?
0
...
It seems multifile mode is switched off completely:
...
$ readelf -S 1 2 3 4 | grep -c "\.gnu_debugaltlink"
0
...
It could at least support one pointer size.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-13 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 vries at gcc dot gnu.org [this message]
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
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@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).