[Bug gas/20703] [gas][x86] Cannot assemble certain registers for vpmuludq instruction

2016-10-17 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20703

H.J. Lu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
   Last reconfirmed||2016-10-17
 CC||hjl.tools at gmail dot com
 Ever confirmed|0   |1

--- Comment #1 from H.J. Lu  ---
[hjl@gnu-6 mbind]$ cat x.s
vpmuludq 0x420(%r9),%xmm29,%xmm16
[hjl@gnu-6 mbind]$ gcc -c x.s
[hjl@gnu-6 mbind]$ objdump -dwr x.o

x.o: file format elf64-x86-64


Disassembly of section .text:

 <.text>:
   0:   62 c1 95 00 f4 41 42vpmuludq 0x420(%r9),%xmm29,%xmm16
[hjl@gnu-6 mbind]$

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20710] New: [libopcodes][x86] libopcodes produces "(bad)" decode for certain sal instructions

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20710

Bug ID: 20710
   Summary: [libopcodes][x86] libopcodes produces "(bad)" decode
for certain sal instructions
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following bytes correspond to a 2-byte sal instruction, but libpocodes
produces a 1-byte "(bad)" output instead.

Bytes: d2 f0
Expected output: salb %cl, %al

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20709] New: [libopcodes][x86]Failure to disassemble variant encoding of test instruction

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20709

Bug ID: 20709
   Summary: [libopcodes][x86]Failure to disassemble variant
encoding of test instruction
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following are the bytes of a test instruction and the expected output.
Libopcodes returns a "(bad)" instruction when disassembling these bytes.

Bytes: f6 0b 50
Expected output: test $0x50,(%rbx)

The other possible encoding of this instruction is f6 03 50.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20706] New: [libopcodes][x86] invalid quadword XOP instructions using %ymm registers

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20706

Bug ID: 20706
   Summary: [libopcodes][x86] invalid quadword XOP instructions
using %ymm registers
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following are examples of objdump output XOP instructions using %ymm
registers that produce invalid size errors.

Bytes: 8f a9 d6 93 52 07
Instruction: vprotq 0x7(%rdx), %xmm5, %ymm2

Bytes: 8f 29 34 9b 37
Instruction: vpshaq %xmm9, (%rdi), %ymm14

In addition to producing errors if assembled, these bytes are interpreted as an
invalid instruction by other decoders.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20705] New: [libopcodes][x86] VEX masking register name lacks formatting, cannot assemble

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20705

Bug ID: 20705
   Summary: [libopcodes][x86] VEX masking register name lacks
formatting, cannot assemble
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following instruction produced by objdump cannot be assembled with gas due
to an error.

Bytes: c5 ac 46 f5
Instruction: kxnorw %k5, k2, %k6
ERROR: operand size mismatch for `kxnorw'

By changing the second operand to "%k2" instead of "k2", the output could be
reassembled. I'm not sure if this should be reported to gas as well to allow
the "k2" syntax in addition to "%k2", but I think objdump should be producing
valid assembly regardless.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20704] [libopcodes][x86] Decodes in valid PTEST instruction as opcode with no operands.

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20704

--- Comment #1 from nholcomb at wisc dot edu ---
The following bytes produce only the opcode when decoded. The bytes themselves
do not appear to be a valid instruction.

Bytes: 0f 7a 20 72
Output: ptest

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20704] [libopcodes][x86] Decodes in valid PTEST instruction as opcode with no operands.

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20704

nholcomb at wisc dot edu changed:

   What|Removed |Added

Summary|[libopcodes][x86]   |[libopcodes][x86] Decodes
   ||in valid PTEST instruction
   ||as opcode with no operands.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20704] New: [libopcodes][x86]

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20704

Bug ID: 20704
   Summary: [libopcodes][x86]
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug gas/20703] New: [gas][x86] Cannot assemble certain registers for vpmuludq instruction

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20703

Bug ID: 20703
   Summary: [gas][x86] Cannot assemble certain registers for
vpmuludq instruction
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: gas
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following instruction produced by objdump cannot be assembled by GAS due to
an error:

Bytes: 62 c1 95 00 f4 41 42
Instruction: vpmuludq 0x420(%r9), %xmm29, %xmm16
ERROR:  invalid register operand for `vpmuludq'

This might be a limitation on the part of gas. Checking other decoders like XED
and LLVM, the instruction appears to be valid.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20702] New: [libopcodes][x86] Invalid suffix for sysret instruction due to data16 prefix

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20702

Bug ID: 20702
   Summary: [libopcodes][x86] Invalid suffix for sysret
instruction due to data16 prefix
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following instruction (output of objdump) could not be assembled using GAS
due to the error:

Bytes: 66 0f 07
Instruction: sysretw
ERROR: invalid instruction suffix for `sysret'

I would guess that this has to do with the data16 prefix on the sysret.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20701] New: [libopcodes][x86] Invalid suffix for phaddw instruction

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20701

Bug ID: 20701
   Summary: [libopcodes][x86] Invalid suffix for phaddw
instruction
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The following instruction (output of objdump) could not be assembled using GAS
due to the error:

Bytes: 0f 7a 47 22
Instruction: phaddwq (%rdx), %xmm4
ERROR: invalid instruction suffix for `phaddw'

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20700] New: [libopcodes][x86] Invalid suffix for xbegin

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=20700

Bug ID: 20700
   Summary: [libopcodes][x86] Invalid suffix for xbegin
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: nholcomb at wisc dot edu
  Target Milestone: ---

The xbegin instruction should only works with 16-bit or 32-bit offsets, so the
'q' suffix is invalid.

Bytes: c7 f8 80 aa 33 90
Output: xbeginq 0x9033aa86

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/19660] [libopcodes] [x86] REP prefixes shown incorrectly

2016-10-17 Thread nholcomb at wisc dot edu
https://sourceware.org/bugzilla/show_bug.cgi?id=19660

--- Comment #6 from nholcomb at wisc dot edu ---
The fact that the rep prefixes cannot be used with these opcodes is not the
same as machine dependencies. This instruction will be invalid everywhere, so
it should be decoded as invalid.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/20699] New: [libopcodes][x86] Decodes invalid 32-bit address for a 64-bit MPX instruction

2016-10-17 Thread njholcomb at wi dot rr.com
https://sourceware.org/bugzilla/show_bug.cgi?id=20699

Bug ID: 20699
   Summary: [libopcodes][x86] Decodes invalid 32-bit address for a
64-bit MPX instruction
   Product: binutils
   Version: 2.26
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: binutils
  Assignee: unassigned at sourceware dot org
  Reporter: njholcomb at wi dot rr.com
  Target Milestone: ---

Libopcodes produces invalid 32-bit address for a 64-bit MPX instruction.

Output: addr32 bndstx %bnd0, -0x76a5963e(%eip) # 0x895a69cb
Bytes: 67 41 0f 1b 05 c2 69 5a 89

This instruction should be shown as invalid because 64-bit MPX instructions
cannot act on 32-bit addresses.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug gold/20693] kernel build error on ppc64le

2016-10-17 Thread markus at trippelsdorf dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=20693

--- Comment #1 from Markus Trippelsdorf  ---
It happens on all archs with an empty archive.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug gas/20692] gas failed on SPARC

2016-10-17 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20692

--- Comment #3 from Nick Clifton  ---
Hi Igor,

>> You could try adding "-D.volatile= -D.nonvolatile= -Wa,--no-relax" to the

> your solution doesn't work.
> GAS command line on SPARC not accepted -Wa,--no-relax
> we can use -no-relax 

Oops - I had too many dashes, sorry about that.

> - but it is not fixed my problem 

Well, it does fix the assembler problem you had.  Now you have a linker/
source file problem.

> and i can see:

> Text relocation remains referenced
> against symbol  offset  in file
> _GLOBAL_OFFSET_TABLE_   0x214   pics/_rtbootld.o
> _GLOBAL_OFFSET_TABLE_   0x194   pics/door.o

> ld: fatal: relocations remain against allocatable but non-writable sections

Well the linker error messages seems pretty clear.  My guess would be
that _rtbootld.o and door.o come from assembler source files, or else 
C/C++ source files containing inline assembler directives, and that
they are creating special sections of their own.  Can you modify the
sources files ?  If so you could use "objdump -r pics/"
to find out which sections have these problematic relocations, and
then you could edit the sources to add the writeable attribute to the
section declarations.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


Re: [Bug gas/20692] gas failed on SPARC

2016-10-17 Thread Nick Clifton
Hi Igor,

>> You could try adding "-D.volatile= -D.nonvolatile= -Wa,--no-relax" to the

> your solution doesn't work.
> GAS command line on SPARC not accepted -Wa,--no-relax
> we can use -no-relax 

Oops - I had too many dashes, sorry about that.

> - but it is not fixed my problem 

Well, it does fix the assembler problem you had.  Now you have a linker/
source file problem.

> and i can see:

> Text relocation remains referenced
> against symbol  offset  in file
> _GLOBAL_OFFSET_TABLE_   0x214   pics/_rtbootld.o
> _GLOBAL_OFFSET_TABLE_   0x194   pics/door.o

> ld: fatal: relocations remain against allocatable but non-writable sections

Well the linker error messages seems pretty clear.  My guess would be
that _rtbootld.o and door.o come from assembler source files, or else 
C/C++ source files containing inline assembler directives, and that
they are creating special sections of their own.  Can you modify the
sources files ?  If so you could use "objdump -r pics/"
to find out which sections have these problematic relocations, and
then you could edit the sources to add the writeable attribute to the
section declarations.

Cheers
  Nick


___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug gas/20692] gas failed on SPARC

2016-10-17 Thread ikozhukhov at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20692

--- Comment #2 from Igor Kozhukhov  ---
(In reply to Nick Clifton from comment #1)
> (In reply to Igor Kozhukhov from comment #0)
>  
> > ./crt/_rtbootld.s:75: Error: unknown pseudo-op: `.volatile'
> > ./crt/_rtbootld.s:245: Error: unknown pseudo-op: `.nonvolatile'
>  
> > what is replacement for .volatile on GAS?
> 
> There is no direct replacement.  If I have read the Sparc Assembly Language
> Reference Manual correctly, then these pseudo ops allow (.nonvolatile) and
> disallow (.volatile) assembly time optimizations.  The only optimization
> that GAS performs for the Sparc architecture is jump/call relaxation, and
> this is controlled via a command line option, not a pseudo-op.
> 
> You could try adding "-D.volatile= -D.nonvolatile= -Wa,--no-relax" to the
> command line and see if this works.
> 
> Cheers
>   Nick

your solution doesn't work.
GAS command line on SPARC not accepted -Wa,--no-relax
we can use -no-relax - but it is not fixed my problem and i can see:

/usr/bin/ld -32 -o libc.so.1 -G -hlibc.so.1 -ztext -zdefs -Bdirect 
-M/ws/builds/igork/dg-54/usr/src/lib/libc/port/mapfile-vers
-M/ws/builds/igork/dg-54/usr/src/common/mapfiles/common/map.pagealign  -z
rtldinfo=tls_rtldinfo -znow -e __rtboot  -zdtrace=dtrace_data pics/crti.o
pics/stret1.opics/stret2.o   pics/stret4.o  
pics/_ftou.opics/cerror.o   pics/cerror64.o
pics/hwmuldiv.o pics/_rtbootld.o   
pics/_D_cplx_div.o  pics/_D_cplx_div_ix.o   pics/_D_cplx_div_rx.o  
pics/_D_cplx_mul.o  pics/_F_cplx_div.o 
pics/_F_cplx_div_ix.o   pics/_F_cplx_div_rx.o   pics/_F_cplx_mul.o 
pics/_Q_add.o   pics/_Q_cmp.o   pics/_Q_cmpe.o 
pics/_Q_cplx_div.o  pics/_Q_cplx_div_ix.o   pics/_Q_cplx_div_rx.o  
pics/_Q_cplx_lr_div.o   pics/_Q_cplx_lr_div_ix.o   
pics/_Q_cplx_lr_div_rx.opics/_Q_cplx_lr_mul.o   pics/_Q_cplx_mul.o 
pics/_Q_div.o   pics/_Q_dtoq.o  pics/_Q_fcc.o  
pics/_Q_itoq.o  pics/_Q_lltoq.o pics/_Q_mul.o  
pics/_Q_neg.o   pics/_Q_qtod.o  pics/_Q_qtoi.o 
pics/_Q_qtos.o  pics/_Q_qtou.o  pics/_Q_scl.o  
pics/_Q_set_except.opics/_Q_sqrt.o  pics/_Q_stoq.o 
pics/_Q_sub.o   pics/_Q_ulltoq.opics/_Q_utoq.o 
pics/__quad_mag.o   pics/_Q_get_rp_rd.o
pics/fpgetmask.opics/fpgetrnd.o
pics/fpgetsticky.o  pics/fpsetmask.opics/fpsetrnd.o
pics/fpsetsticky.o pics/__quad.opics/atomic.o  
pics/chacha.o   pics/xattr_common.o pics/bcmp.o
pics/bcopy.opics/bzero.o   
pics/bsearch.o  pics/memccpy.o  pics/qsort.o   
pics/strtol.o   pics/strtoul.o  pics/strtoll.o 
pics/strtoull.o pics/dtrace_data.o  pics/_getsp.o  
pics/_xregs_clrptr.opics/abs.o 
pics/alloca.o   pics/arc4random.o  
pics/arc4random_uniform.o   pics/ascii_strcasecmp.o
pics/byteorder.opics/cuexit.o   pics/ecvt.o
pics/endian.o   pics/errlst.o   pics/getctxt.o 
pics/ladd.o pics/lmul.o pics/lock.o
pics/lshiftl.o  pics/lsign.o   
pics/lsub.o pics/makectxt.o pics/memchr.o  
pics/memcmp.o   pics/new_list.o pics/setjmp.o  
pics/siginfolst.o   pics/siglongjmp.o  
pics/smt_pause.opics/sparc_data.o   pics/strchr.o  
pics/strcmp.o   pics/strlcpy.o  pics/strncmp.o 
pics/strncpy.o  pics/strnlen.o  pics/swapctxt.o
pics/sync_instruction_memory.o  pics/memcpy.o   pics/memset.o  
pics/memmove.opics/strlen.o pics/strcpy.o  
pics/__flt_decim.o  pics/__flt_rounds.o
pics/__tbl_10_b.o   pics/__tbl_10_h.o  
pics/__tbl_10_s.o   pics/__tbl_2_b.o   
pics/__tbl_2_h.opics/__tbl_2_s.o   
pics/__tbl_fdq.opics/__tbl_tens.o  
pics/__x_power.opics/_base_sup.opics/aconvert.o
pics/decimal_bin.o  pics/double_decim.o
pics/econvert.o pics/fconvert.o
pics/file_decim.o   pics/finite.o   pics/fp_data.o 
pics/func_decim.o   pics/gconvert.o 

[Bug gas/20692] gas failed on SPARC

2016-10-17 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=20692

Nick Clifton  changed:

   What|Removed |Added

 CC||nickc at redhat dot com

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

> ./crt/_rtbootld.s:75: Error: unknown pseudo-op: `.volatile'
> ./crt/_rtbootld.s:245: Error: unknown pseudo-op: `.nonvolatile'

> what is replacement for .volatile on GAS?

There is no direct replacement.  If I have read the Sparc Assembly Language
Reference Manual correctly, then these pseudo ops allow (.nonvolatile) and
disallow (.volatile) assembly time optimizations.  The only optimization that
GAS performs for the Sparc architecture is jump/call relaxation, and this is
controlled via a command line option, not a pseudo-op.

You could try adding "-D.volatile= -D.nonvolatile= -Wa,--no-relax" to the
command line and see if this works.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug ld/20694] New: PDP11 TARGET_PAGE_SIZE is incorrect

2016-10-17 Thread casner at acm dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=20694

Bug ID: 20694
   Summary: PDP11 TARGET_PAGE_SIZE is incorrect
   Product: binutils
   Version: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: ld
  Assignee: unassigned at sourceware dot org
  Reporter: casner at acm dot org
  Target Milestone: ---

The file ld/emulparams/pdp11.sh includes the line:

TARGET_PAGE_SIZE=256

The actual page size of the memory management hardware on the PDP11/45,
PDP11/70, etc. is 8192 bytes.  A consequence of this error is that the data
section in a.out format output is not offset to a page boundary.

I have verified that the UNIX V6 ld program running on a simulated PDP11 does
offset the data section to the next page boundary (2 octal) when the -n
option is included.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug gold/20693] New: kernel build error on ppc64le

2016-10-17 Thread markus at trippelsdorf dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=20693

Bug ID: 20693
   Summary: kernel build error on ppc64le
   Product: binutils
   Version: 2.28 (HEAD)
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: gold
  Assignee: ccoutant at gmail dot com
  Reporter: markus at trippelsdorf dot de
CC: ian at airs dot com
  Target Milestone: ---

On ppc64le I get during Linux kernel build:

objdump -h lib/lib.a | sed -ne '/___ksymtab/{s/.*+/EXTERN(/;s/ .*/)/;p}'
>lib/.lib-ksyms.o.lds; rm -f lib/.lib_exports.o; ar rcsD lib/.lib_exports.o; ld
-EL-r -o lib/lib-ksyms.o -T lib/.lib-ksyms.o.lds lib/.lib_exports.o; rm
lib/.lib_exports.o lib/.lib-ksyms.o.lds
ld: internal error in target, at parameters.h:105


trippels@gcc2-power8 linux % rm foo.o
trippels@gcc2-power8 linux % ar rcsD foo.o
trippels@gcc2-power8 linux % cat foo.o
!
trippels@gcc2-power8 linux % cat test.lds
EXTERN(bar)
trippels@gcc2-power8 linux % ld.bfd -T test.lds foo.o
trippels@gcc2-power8 linux % ld.gold -T test.lds foo.o
ld.gold: internal error in target, at parameters.h:105

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils