[Bug binutils/31384] New: ar.exe: could not create temporary file whilst writing archive: Permission denied
https://sourceware.org/bugzilla/show_bug.cgi?id=31384 Bug ID: 31384 Summary: ar.exe: could not create temporary file whilst writing archive: Permission denied Product: binutils Version: 2.41 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: stanislav.simek at siemens dot com Target Milestone: --- Hello all, We are using gcc 13.2.0 together with binutils in version 2.41. Our build machines can execute like ~ 20 parallel execution of ar(.exe) and time to time get this error: ar.exe: could not create temporary file whilst writing archive: Permission denied It is sporadic, if we clean all and build again no problem occurs. Any idea what could be wrong? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28448] Memory leak in function add_symbols(plugin.c) from bfd linker
https://sourceware.org/bugzilla/show_bug.cgi?id=28448 --- Comment #1 from Sourceware Commits --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=19bfbfa6659c7733d3148dcce5125a0eb3fd9670 commit 19bfbfa6659c7733d3148dcce5125a0eb3fd9670 Author: Alan Modra Date: Thu Feb 15 16:55:59 2024 +1030 PR28448, Memory leak in function add_symbols(plugin.c) PR 28448 * plugin.c (add_symbols): bfd_alloc memory for symptrs. Check bfd_make_empty_symbol return. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28448] Memory leak in function add_symbols(plugin.c) from bfd linker
https://sourceware.org/bugzilla/show_bug.cgi?id=28448 Alan Modra changed: What|Removed |Added Target Milestone|--- |2.43 Status|UNCONFIRMED |RESOLVED Assignee|unassigned at sourceware dot org |amodra at gmail dot com Resolution|--- |FIXED --- Comment #2 from Alan Modra --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug.
Issue 66395 in oss-fuzz: binutils:fuzz_nm: Out-of-memory in fuzz_nm
Updates: Labels: -restrict-view-commit Comment #3 on issue 66395 by sheriffbot: binutils:fuzz_nm: Out-of-memory in fuzz_nm https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66395#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 gas/31388] There is no documentation for -moperand-check
https://sourceware.org/bugzilla/show_bug.cgi?id=31388 H.J. Lu changed: What|Removed |Added Summary|There is no document for|There is no documentation |-moperand-check |for -moperand-check -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31388] New: There is no document for -moperand-check
https://sourceware.org/bugzilla/show_bug.cgi?id=31388 Bug ID: 31388 Summary: There is no document for -moperand-check Product: binutils Version: 2.43 (HEAD) Status: NEW Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: jbeulich at suse dot com Target Milestone: --- commit 7bab8ab56f7c09acbaca2645314e0622b20c2afe Author: Jan Beulich Date: Tue Aug 7 16:55:00 2012 + The VGATHER group of instructions requires that all three involved xmm/ymm registers are distinct. This patch adds code to check for this, and at once eliminates a superfluous check for not using PC-relative addressing for these instructions (the fact that an index register is required here already excludes valid PC-relative addresses). The severity of the resulting diagnostics can be controlled via command line option or directive. added the assembler option, -moperand-check. But there is no documentation for this option. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31389] New: Wrong default for -msse-check is displayed
https://sourceware.org/bugzilla/show_bug.cgi?id=31389 Bug ID: 31389 Summary: Wrong default for -msse-check is displayed Product: binutils Version: 2.43 (HEAD) Status: NEW Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com Target Milestone: --- Target: x86 commit 7c5c05effd92cc5732bee527303077fc2e6b62af Author: H.J. Lu Date: Thu Aug 9 09:48:12 2018 -0700 x86: Display default x86-specific options for "as --help" * config/tc-i386.c (md_show_usage): Display default options. has fprintf (stream, _("\ - -msse-check=[none|error|warning]\n\ + -msse-check=[none|error|warning] (default: warning)\n\ check SSE instructions\n")); But its default it none: static enum check_kind { check_none = 0, check_warning, check_error } sse_check, operand_check = check_warning; -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31389] Wrong default for -msse-check is displayed
https://sourceware.org/bugzilla/show_bug.cgi?id=31389 --- Comment #1 from Sourceware Commits --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7a6a03c499ad899c1d1dd93beccbb62795feb1db commit 7a6a03c499ad899c1d1dd93beccbb62795feb1db Author: H.J. Lu Date: Thu Feb 15 15:00:31 2024 -0800 x86: Display -msse-check= default as none Display -msse-check= default as none for "as --help" since its default is none, not warning. PR gas/31389 * config/tc-i386.c (md_show_usage): Change -msse-check= default to none. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31389] Wrong default for -msse-check is displayed
https://sourceware.org/bugzilla/show_bug.cgi?id=31389 --- Comment #2 from Sourceware Commits --- The binutils-2_42-branch branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=553c7f61b74badf91df484450944675efd9cd485 commit 553c7f61b74badf91df484450944675efd9cd485 Author: H.J. Lu Date: Thu Feb 15 15:00:31 2024 -0800 x86: Display -msse-check= default as none Display -msse-check= default as none for "as --help" since its default is none, not warning. PR gas/31389 * config/tc-i386.c (md_show_usage): Change -msse-check= default to none. (cherry picked from commit 7a6a03c499ad899c1d1dd93beccbb62795feb1db) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28124] ld: Make special sections in a section group GCable
https://sourceware.org/bugzilla/show_bug.cgi?id=28124 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed||2024-02-16 --- Comment #2 from Alan Modra --- It isn't that SHT_INIT_ARRAY sections are treated specially (although they are for ld -r). The reason why .init_array.bbb and .init_array.a is kept is the KEEP in the default linker script: .init_array: { PROVIDE_HIDDEN (__init_array_start = .); KEEP (*(SORT_BY_INIT_PRIORITY(.init_array.*) SORT_BY_INIT_PRIORITY(.ctors.*))) KEEP (*(.init_array EXCLUDE_FILE (*crtbegin.o *crtbegin?.o *crtend.o *crtend?.o ) .ctors)) PROVIDE_HIDDEN (__init_array_end = .); } The pattern .init_array.* is there to match .init_array.65530 or similar with a numeric suffix. (In fact, it's probably wrong to match other named .init_array sections there, but that's a side issue.) KEEP operates on the named sections regardless of whether they are part of a group or not. We'd need to change the behaviour of KEEP (or invent a new keyword) if .init_array inside a group was to be gc'ed. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28072] Hard coded plural in readelf.c
https://sourceware.org/bugzilla/show_bug.cgi?id=28072 Alan Modra changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Alan Modra --- Fixed then.. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/31389] Wrong default for -msse-check is displayed
https://sourceware.org/bugzilla/show_bug.cgi?id=31389 Sam James changed: What|Removed |Added CC||sam at gentoo dot org Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |2.43 --- Comment #3 from Sam James --- . -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27949] Segfault and core dump
https://sourceware.org/bugzilla/show_bug.cgi?id=27949 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |OBSOLETE --- Comment #3 from Alan Modra --- No useful info to do anything with this bug report, so closing. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27923] ld: Support DT_RELR relative relocation format
https://sourceware.org/bugzilla/show_bug.cgi?id=27923 --- Comment #6 from Alan Modra --- Also supported on powerpc64 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27865] Unsupported name-unmangling for C++20 modules?
https://sourceware.org/bugzilla/show_bug.cgi?id=27865 Alan Modra changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Alan Modra --- As per comment #6 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27708] strip mishandles padding between notes
https://sourceware.org/bugzilla/show_bug.cgi?id=27708 Alan Modra changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Alan Modra --- Fixed -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27597] nios: assertion fail elf32-nios2.c:1881
https://sourceware.org/bugzilla/show_bug.cgi?id=27597 Alan Modra changed: What|Removed |Added Assignee|unassigned at sourceware dot org |amodra at gmail dot com Last reconfirmed||2024-02-16 Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Alan Modra --- A litte bit of source digging says the assertion failure is from the BFD_ASSERT in nios2_elf32_install_imm16, and since every call except one to that function masks the value, the assert is rather pointless. The exception is: nios2_elf32_install_imm16 (splt, h->plt.offset + 8, 0xfff4 - h->plt.offset); in nios2_elf32_finish_dynamic_symbol, so it seems we have a PLT size overflow. -- You are receiving this mail because: You are on the CC list for the bug.