https://sourceware.org/bugzilla/show_bug.cgi?id=24165
Martin Liška changed:
What|Removed |Added
CC||marxin.liska at gmail dot com
--- Comm
https://sourceware.org/bugzilla/show_bug.cgi?id=24168
Bug ID: 24168
Summary: segment fault in nm-new in binutils-2.30
Product: binutils
Version: 2.30
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: b
https://sourceware.org/bugzilla/show_bug.cgi?id=24167
Bug ID: 24167
Summary: segment fault in objdump in binutils-2.26
Product: binutils
Version: 2.26
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component:
https://sourceware.org/bugzilla/show_bug.cgi?id=24165
--- Comment #1 from Serge Belyshev ---
The problem can be reproduced with synthetic testcase generated like this:
yes .p2align 5 | head -n50 > bug.s
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://sourceware.org/bugzilla/show_bug.cgi?id=24165
Bug ID: 24165
Summary: fivefold time and memory usage since commit 3ae729d5
on large files generated by lto
Product: binutils
Version: 2.33 (HEAD)
Status: UNCONFIRMED
Hi Dmitry,
> Still, even this way, 400 bytes is more then twice as big, compared to
> fasm. Any suggestions, how to shrink binary futher?
This might be because the linker defaults to page aligning the binaries.
Have you tried linking with the --nmagic option ? (Or alternatively the
--omagic opti
