[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 --- Comment #6 from John David Anglin --- Probably, the issue is caused by this code in elf64-hppa.c: /* Force DT_FLAGS to always be set. Required by HPUX 11.00 patch PHSS_26559. */ if (!add_dynamic_entry (DT_FLAGS, (info)->flags)) return false; Maybe this should be limited to HPUX? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 --- Comment #5 from H.J. Lu --- (In reply to dave.anglin from comment #4) > On 2024-04-12 5:58 a.m., nickc at redhat dot com wrote: > > I am not sure why this is happening, but I do not see the harm in it. So I > > think that the best solution is to change the now-3 test to look for the old > > flags. > There is this comment in include/elf/hppa.h" > /* Processor specific dynamic array tags. */ > > /* Arggh. HP's tools define these symbols based on the > old value of DT_LOOS. So we must do the same to be > compatible. */ > #define DT_HP_LOAD_MAP (OLD_DT_LOOS + 0x0) > [...] > /* Values for DT_HP_DLD_FLAGS. */ > #define DT_HP_DEBUG_PRIVATE 0x1 /* Map text private */ > #define DT_HP_DEBUG_CALLBACK 0x2 /* Callback */ > #define DT_HP_DEBUG_CALLBACK_BOR 0x4 /* BOR callback */ > #define DT_HP_NO_ENVVAR 0x8 /* No env var */ > #define DT_HP_BIND_NOW 0x00010 /* Bind now */ Why does it apply to hppa-linux? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/31611] bfd: bfdio using shlwapi (win32) functionality without linking
https://sourceware.org/bugzilla/show_bug.cgi?id=31611 Simon Marchi changed: What|Removed |Added CC||simon.marchi at polymtl dot ca -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/31123] improvements to hardware event implementation
https://sourceware.org/bugzilla/show_bug.cgi?id=31123 Kurt Goebel changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 --- Comment #4 from dave.anglin at bell dot net --- On 2024-04-12 5:58 a.m., nickc at redhat dot com wrote: > I am not sure why this is happening, but I do not see the harm in it. So I > think that the best solution is to change the now-3 test to look for the old > flags. There is this comment in include/elf/hppa.h" /* Processor specific dynamic array tags. */ /* Arggh. HP's tools define these symbols based on the old value of DT_LOOS. So we must do the same to be compatible. */ #define DT_HP_LOAD_MAP (OLD_DT_LOOS + 0x0) [...] /* Values for DT_HP_DLD_FLAGS. */ #define DT_HP_DEBUG_PRIVATE 0x1 /* Map text private */ #define DT_HP_DEBUG_CALLBACK 0x2 /* Callback */ #define DT_HP_DEBUG_CALLBACK_BOR 0x4 /* BOR callback */ #define DT_HP_NO_ENVVAR 0x8 /* No env var */ #define DT_HP_BIND_NOW 0x00010 /* Bind now */ -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31255] keyword arguments do not work with .altmacro
https://sourceware.org/bugzilla/show_bug.cgi?id=31255 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Assignee|unassigned at sourceware dot org |nickc at redhat dot com Resolution|--- |FIXED CC||nickc at redhat dot com --- Comment #2 from Nick Clifton --- Hi Seanga, Thanks for reporting this problem. I have checked in a small patch to update the assembler's documentation. The .altmacro entry now includes: 'No passing arguments to macros based upon keyword assignment.' In altmacro mode arguments cannot be passed to macros by keyword assignment. and the .macro entry includes: Note however that when operating in altmacro mode arguments can only be specified by position, not keyword. Thus for example: .altmacro .macro foo bar=1, baz=2 .print "\bar \baz" .endm foo baz=3 Will print: baz=3 2 Rather than the expected: 1 3 Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31255] keyword arguments do not work with .altmacro
https://sourceware.org/bugzilla/show_bug.cgi?id=31255 --- Comment #1 from Sourceware Commits --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=99daf56f4b4bf831bb29bffb79f2172f1b316cb9 commit 99daf56f4b4bf831bb29bffb79f2172f1b316cb9 Author: Nick Clifton Date: Fri Apr 12 16:51:51 2024 +0100 Update description of macro keyword argument assignment in assembler documentation. PR 31255 -- You are receiving this mail because: You are on the CC list for the bug.
Issue 67866 in oss-fuzz: binutils:fuzz_objdump: Direct-leak in _bfd_mmap_read_temporary
Updates: Labels: -restrict-view-commit Comment #3 on issue 67866 by sheriffbot: binutils:fuzz_objdump: Direct-leak in _bfd_mmap_read_temporary https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67866#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 67902 in oss-fuzz: binutils:fuzz_objcopy: Undefined-shift in setup_section
Updates: Labels: -restrict-view-commit Comment #3 on issue 67902 by sheriffbot: binutils:fuzz_objcopy: Undefined-shift in setup_section https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67902#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 --- Comment #3 from H.J. Lu --- (In reply to Nick Clifton from comment #2) > Created attachment 15461 [details] > Proposed patch Why should --disable-new-dtags generate new tags? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30730] Building libheif for m68k_cf fails with Internal error in emit_expr_encoded at dw2gencfi.c:215
https://sourceware.org/bugzilla/show_bug.cgi?id=30730 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com Assignee|unassigned at sourceware dot org |nickc at redhat dot com --- Comment #1 from Nick Clifton --- Hi Giulio, Thanks for reporting this problem. Please could you upload the assembler output from the compiler (created when you add -S to the gcc command line), plus the command line that gcc invokes when it runs the assembler (use -v to see this). If you are using binutils 2.26.1 then I should point out that this is a really old release (we are up to version 2.42 now) and so it is quite likely that the bug has already been fixed. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 --- Comment #2 from Nick Clifton --- Created attachment 15461 --> https://sourceware.org/bugzilla/attachment.cgi?id=15461=edit Proposed patch -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30743] FAIL: ld-elf/now-3 for hppa64-*-linux* target
https://sourceware.org/bugzilla/show_bug.cgi?id=30743 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com Assignee|unassigned at sourceware dot org |nickc at redhat dot com Status|NEW |ASSIGNED --- Comment #1 from Nick Clifton --- Hi Dave, This is slightly strange. The test is meant to check that the old style dynamic tags for BIND_NOW are generated, ie: $ readelf -d -W tmpdir/dump [...] 0x0018 (BIND_NOW) 0x6ffb (FLAGS_1)Flags: NOW But for the hppa64, both the new *and* old style tags are being generated: $ readelf -d -W tmpdir/dump [...] 0x001e (FLAGS) BIND_NOW 0x0003 (PLTGOT) 0x1308 0x0018 (BIND_NOW) 0x6ffb (FLAGS_1)Flags: NOW I am not sure why this is happening, but I do not see the harm in it. So I think that the best solution is to change the now-3 test to look for the old flags. Would you mind giving the uploaded patch a try and let me know if it works for you ? Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
