[Bug binutils/31283] windmc (s390x) fails with: parser: syntax error

2024-01-24 Thread rjones at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31283

Richard Jones  changed:

   What|Removed |Added

 CC||rjones at redhat dot com

--- Comment #2 from Richard Jones  ---
Created attachment 15329
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15329&action=edit
0001-binutils-windmc-Parse-input-correctly-on-big-endian-.patch

Potential fix

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


[Bug binutils/31283] windmc (s390x) fails with: parser: syntax error

2024-01-24 Thread dan at danny dot cz
https://sourceware.org/bugzilla/show_bug.cgi?id=31283

--- Comment #3 from Dan Horak  ---
LGTM(In reply to Richard Jones from comment #2)
> Created attachment 15329 [details]
> 0001-binutils-windmc-Parse-input-correctly-on-big-endian-.patch
> 
> Potential fix

LGTM, thanks.

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


[Bug binutils/31283] windmc (s390x) fails with: parser: syntax error

2024-01-24 Thread rjones at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31283

--- Comment #4 from Richard Jones  ---
v2:

https://sourceware.org/pipermail/binutils/2024-January/132096.html

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


[Bug ld/31289] New: --fatal-warnings doesn't work for command-line options

2024-01-24 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31289

Bug ID: 31289
   Summary: --fatal-warnings doesn't work for command-line options
   Product: binutils
   Version: 2.43 (HEAD)
Status: NEW
  Severity: normal
  Priority: P2
 Component: ld
  Assignee: unassigned at sourceware dot org
  Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

For example:

$ ld.bfd -z bad-option --fatal-warnings -e 0/dev/null
ld.bfd: warning: -z bad-option ignored
$ echo $?
0

ie the warning about the ignored option is not being treated as an
error.  This happens because the --fatal-warnings option only takes
affect after it has been processed, and we process the options in a
linear order.  So the following works:

$ ld.bfd --fatal-warnings -z bad-option -e 0 /dev/null
ld.bfd: warning: -z bad-option ignored
$ echo $?
1

This behaviour differs from gold and lld, both of which honour
--fatal-warnings no matter where it occurs on the command line.

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


[Bug ld/31289] --fatal-warnings doesn't work for command-line options

2024-01-24 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31289

--- Comment #1 from H.J. Lu  ---
Also it looks strange:

$ ld.bfd --fatal-warnings -z bad-option -e 0 /dev/null
ld.bfd: warning: -z bad-option ignored
$ echo $?
1

Why do we say "warning: -z bad-option ignored" when it is an error.

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


[Bug ld/31289] --fatal-warnings doesn't work for command-line options

2024-01-24 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31289

Sam James  changed:

   What|Removed |Added

 CC||sam at gentoo dot org

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