https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #8 from Achim ---
I've built 2.42 again with this patch applied and it fixes the problem (the
objdump disassembly now correctly shows Keyboard.xs as the source file).
--
You are receiving this mail because:
You are on the CC list
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #6 from Achim ---
Created attachment 15079
--> https://sourceware.org/bugzilla/attachment.cgi?id=15079&action=edit
Keyword.dll (unstripped binary)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30725
--- Comment #4 from Achim ---
Looking at the code in objdump, it relies on bfd to return the line number
information in constant time. This is what _should_ be happening if the
debuginfo stash is actually working, but apparently it either doe
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #4 from Achim ---
Looking into Keyword.c (compilation unit) it is easy to see that the correct
entry is line 37 in Keyword.xs for the first entry point. The corresponding
line in Keyword.c would be line 46, but that was not emitte
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #3 from Achim ---
Created attachment 15075
--> https://sourceware.org/bugzilla/attachment.cgi?id=15075&action=edit
Keyword.c
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
Achim changed:
What|Removed |Added
Attachment #15074|Keywords.xs |Keyword.xs
description|
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #2 from Achim ---
Created attachment 15074
--> https://sourceware.org/bugzilla/attachment.cgi?id=15074&action=edit
Keywords.xs
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30783
--- Comment #1 from Achim ---
Created attachment 15073
--> https://sourceware.org/bugzilla/attachment.cgi?id=15073&action=edit
objdump -wWL
--
You are receiving this mail because:
You are on the CC list for the bug.
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: Stromeko at nexgo dot de
Target Milestone: ---
Created attachment 15072
--> https://sourceware.org/bugzilla/attachment.cgi?id=15072&action=edit
https://sourceware.org/bugzilla/show_bug.cgi?id=30724
--- Comment #13 from Achim ---
Thank you.
Going forward I'd suggest you revisit why you need to turn around the same
stream and if it might not be more efficient to just have a read and a write
stream (really just append I assume) to the same
https://sourceware.org/bugzilla/show_bug.cgi?id=30725
--- Comment #3 from Achim ---
No, the debuginfod is not enabled and the option has no effect other than a
warning about E being an unrecognized debug letter option.
Again, both extracting the line number information from the DWARF5 section an
https://sourceware.org/bugzilla/show_bug.cgi?id=30724
--- Comment #7 from Achim ---
That patch certainly looks more thorough than just reverting the change that
caused the regression… is that on Git somewhere? I can run a tests with it the
upcoming weekend most likely.
Btw, Cygwin and MinGW are
https://sourceware.org/bugzilla/show_bug.cgi?id=30724
--- Comment #4 from Achim ---
As I suspected, the newlib fseek/fseeko implementation flushes the file under
lock (because it punts to fseek_r/fseeko_r) when in append mode and also for
SEEK_CUR before determining the current position (as it ha
https://sourceware.org/bugzilla/show_bug.cgi?id=30725
--- Comment #1 from Achim ---
The preformance regression is unrelated to bug#30724. Results for running
"objdump -l -d" in various versions on the same gcc-11.4 build directory:
objdump 2.39
gcc-ar.exe0.000u 0.000s 0:00.03 0.0% 0
https://sourceware.org/bugzilla/show_bug.cgi?id=30724
--- Comment #3 from Achim ---
(In reply to Andrew Pinski from comment #2)
> That would be then a bug in cygwin stdio code I suspect ...
Maybe, or maybe it actually has to be that way since the wording in POSIX seems
to imply that when certain
https://sourceware.org/bugzilla/show_bug.cgi?id=30724
--- Comment #1 from Achim ---
AFter a few false starts since it seems one really needs to freshly configure
and compile the whole thing each time this got bisected to:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=014a602b86f0
: binutils
Assignee: unassigned at sourceware dot org
Reporter: Stromeko at nexgo dot de
Target Milestone: ---
On Cygwin the performance of objdump has further degraded with 2.41. The
extraction of the debuginfo source files from the objects with "objdump -d -l"
that w
Assignee: unassigned at sourceware dot org
Reporter: Stromeko at nexgo dot de
Target Milestone: ---
On Cygwin there is a massive performance regression during the link phase with
version 2.41. The degradation is superlinear in the number of objects involved
and I have observed
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #10 from Achim ---
(In reply to gee from comment #8)
> Okay, Can I ask why this patch applied in binutils toolchain which targets
> *-mingw32?
That was a mistake that will be fixed in the next release.
> Also, Cygwin/MINGW64(whic
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #6 from Achim ---
So it turns out that removing the section at that commit (as I had done during
bisecting) would actually restore the previuos behaviour (the executable would
not run). Applying the same fix on top of both the 2.3
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #5 from Achim ---
Created attachment 13976
--> https://sourceware.org/bugzilla/attachment.cgi?id=13976&action=edit
Linker map new (ld-2.38 w/patches)
Patch to discard the two DWARF5 sections identified during bisecting applied
(
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #3 from Achim ---
Created attachment 13942
--> https://sourceware.org/bugzilla/attachment.cgi?id=13942&action=edit
Linker map old (ld-2.36)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #2 from Achim ---
Created attachment 13941
--> https://sourceware.org/bugzilla/attachment.cgi?id=13941&action=edit
Linker map new (ld-2.37)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28719
--- Comment #4 from Achim ---
...packages/binutils-gdb/build (2056)# objdump -r weak.o
weak.o: file format pe-x86-64
RELOCATION RECORDS FOR [.text]:
OFFSET TYPE VALUE
0009 IMAGE_REL_AMD64_REL32 __main
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: Stromeko at nexgo dot de
Target Milestone: ---
As detailed in
https://sourceware.org/pipermail/binutils/2021-December/118844.html
commit
25 matches
Mail list logo
