[Bug gas/29052] LoongArch:binutils2.28 are not compatible with the upcoming gcc release 12

2022-04-13 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29052

Nick Clifton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||nickc at redhat dot com
 Resolution|--- |FIXED

--- Comment #1 from Nick Clifton  ---
(In reply to liuzhensong from comment #0)

> Gas used to use parameter -mabi=lp64 (version 2.28), but after

Just to confirm - you are talking about the 2.38 binutils release, not the 2.28
release, correct ?

> commit(2dbf4f28b85d07e9913105e0a93abbec8a376daa) it uses parameter

That number did not reference a real object in the git repository, but I
was able to track down a correct value: 3b14682a432e

> So can binutils2.28 patched this commit?

Done.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29052] LoongArch:binutils2.28 are not compatible with the upcoming gcc release 12

2022-04-13 Thread liuzhensong at loongson dot cn
https://sourceware.org/bugzilla/show_bug.cgi?id=29052

--- Comment #2 from liuzhensong  ---
Sorry, the version number is wrong, it is binutils 2.38 release

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29052] LoongArch:binutils2.28 are not compatible with the upcoming gcc release 12

2022-04-13 Thread liuzhensong at loongson dot cn
https://sourceware.org/bugzilla/show_bug.cgi?id=29052

--- Comment #3 from liuzhensong  ---
(In reply to liuzhensong from comment #2)
> Sorry, the version number is wrong, it is binutils 2.38 release

I will report this bug exactly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29059] New: LoongArch:binutils 2.38 are not compatible with the upcoming gcc release 12

2022-04-13 Thread liuzhensong at loongson dot cn
https://sourceware.org/bugzilla/show_bug.cgi?id=29059

Bug ID: 29059
   Summary: LoongArch:binutils 2.38 are not compatible with the
upcoming gcc release 12
   Product: binutils
   Version: 2.38
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: gas
  Assignee: unassigned at sourceware dot org
  Reporter: liuzhensong at loongson dot cn
  Target Milestone: ---

LoongArch:binutils 2.38 are not compatible with the upcoming gcc release 12

Gas used to use parameter -mabi=lp64 (version 2.38), but after
commit(2dbf4f28b85d07e9913105e0a93abbec8a376daa) it uses parameter -mabi=lp64d.
In gcc12, the parameter -mabi=lp64d will be passed to gas.

So can binutils 2.38 patched this commit?

> commit 2dbf4f28b85d07e9913105e0a93abbec8a376daa
> Author: liuzhensong 
> Date:   Mon Feb 21 14:28:29 2022 +0800
>
>LoongArch: Update ABI eflag in elf header.
>
>  Update LoongArch ABI eflag in elf header.
>ilp32s  0x5
>ilp32f  0x6
>ilp32d  0x7
>lp64s   0x1
>lp64f   0x2
>lp64d   0x3
>
>  bfd/
>* elfnn-loongarch.c Check object flags while ld.
>
>  gas/
>* tc-loongarch.c Write eflag to elf header.
>
>  include/elf
>* loongarch.h Define ABI number.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29059] LoongArch:binutils 2.38 are not compatible with the upcoming gcc release 12

2022-04-13 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=29059

--- Comment #1 from Andreas Schwab  ---
*** Bug 29052 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29052] LoongArch:binutils2.28 are not compatible with the upcoming gcc release 12

2022-04-13 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=29052

Andreas Schwab  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #4 from Andreas Schwab  ---


*** This bug has been marked as a duplicate of bug 29059 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29059] LoongArch:binutils 2.38 are not compatible with the upcoming gcc release 12

2022-04-13 Thread liuzhensong at loongson dot cn
https://sourceware.org/bugzilla/show_bug.cgi?id=29059

liuzhensong  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from liuzhensong  ---
This bug fixed.
commit 2dbf4f28b85d07e9913105e0a93abbec8a376daa had been merged to
binutils-2_38-branch.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/29042] opcodes libtool regression

2022-04-13 Thread macro at orcam dot me.uk
https://sourceware.org/bugzilla/show_bug.cgi?id=29042

Maciej W. Rozycki  changed:

   What|Removed |Added

 CC||macro at orcam dot me.uk

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Issue 45198 in oss-fuzz: binutils:fuzz_as: Direct-leak in xrealloc

2022-04-13 Thread sheriffbot via monorail
Updates:
Labels: -restrict-view-commit

Comment #3 on issue 45198 by sheriffbot: binutils:fuzz_as: Direct-leak in 
xrealloc
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45198#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 43761 in oss-fuzz: binutils:fuzz_as: Direct-leak in xrealloc

2022-04-13 Thread sheriffbot via monorail
Updates:
Labels: -restrict-view-commit -deadline-approaching

Comment #4 on issue 43761 by sheriffbot: binutils:fuzz_as: Direct-leak in 
xrealloc
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43761#c4

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 binutils/29042] opcodes libtool regression

2022-04-13 Thread toolybird at tuta dot io
https://sourceware.org/bugzilla/show_bug.cgi?id=29042

--- Comment #2 from Toolybird  ---
Created attachment 14062
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14062&action=edit
log of failing libtool/linker command invocation

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/29042] opcodes libtool regression

2022-04-13 Thread toolybird at tuta dot io
https://sourceware.org/bugzilla/show_bug.cgi?id=29042

--- Comment #3 from Toolybird  ---
Created attachment 14063
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14063&action=edit
log with --verbose

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/28968] gprofng doesn't build with -Werror=format-security

2022-04-13 Thread toolybird at tuta dot io
https://sourceware.org/bugzilla/show_bug.cgi?id=28968

Toolybird  changed:

   What|Removed |Added

 CC||toolybird at tuta dot io

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29058] Quadratic(?) slowdown of m68k-as on m68k_frob_symbol()

2022-04-13 Thread slyich at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29058

--- Comment #2 from Sergei Trofimovich  ---
Adding a bit of debugging to get the idea what symbol types and values are most
frequent at being checked for alignment:

--- a/gas/config/tc-m68k.c
+++ b/gas/config/tc-m68k.c
@@ -4735,6 +4735,8 @@ m68k_frob_symbol (symbolS *sym)
 {
   struct label_line *l;

+  fprintf(stderr, "m68k_frob_symbol('%s') value = %#lx\n", S_GET_NAME
(sym), S_GET_VALUE (sym));
+
   for (l = labels; l != NULL; l = l->next)
{
  if (l->label == sym)

$ ./as-new a.S
m68k_frob_symbol('%d0') value = 0x1
m68k_frob_symbol('%D0') value = 0x1
m68k_frob_symbol('%d2') value = 0x3
m68k_frob_symbol('%D2') value = 0x3
m68k_frob_symbol('%d4') value = 0x5
m68k_frob_symbol('%D4') value = 0x5
m68k_frob_symbol('%d6') value = 0x7
m68k_frob_symbol('%D6') value = 0x7
m68k_frob_symbol('%a0') value = 0x9
m68k_frob_symbol('%A0') value = 0x9
m68k_frob_symbol('%a2') value = 0xb
m68k_frob_symbol('%A2') value = 0xb
m68k_frob_symbol('%a4') value = 0xd
m68k_frob_symbol('%A4') value = 0xd
m68k_frob_symbol('%a6') value = 0xf
...
m68k_frob_symbol('.LVU1') value = 0x1
m68k_frob_symbol('.LVU3') value = 0x1
m68k_frob_symbol('.LVU5') value = 0x1
m68k_frob_symbol('.LVU7') value = 0x3
m68k_frob_symbol('.LVU11') value = 0x1
m68k_frob_symbol('.LVU13') value = 0x1
...

My guess is that these symbols can't be used as text labels and could be
skipped earlier.

-- 
You are receiving this mail because:
You are on the CC list for the bug.