bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/19145] [regression] arm-none-eabi big-endian LTO broken


From: jonathan at codesourcery dot com
Subject: [Bug binutils/19145] [regression] arm-none-eabi big-endian LTO broken
Date: Fri, 16 Oct 2015 21:47:44 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=19145

--- Comment #2 from Jonathan Roelofs <jonathan at codesourcery dot com> ---
Created attachment 8727
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8727&action=edit
object file compiled from empty source file

$ rm empty.c
$ touch empty.c
$ ./install/bin/arm-none-eabi-gcc -mbig-endian -flto empty.c -save-temps
empty.o: file not recognized: File format is ambiguous
empty.o: matching formats: elf32-bigarm elf32-big
collect2: error: ld returned 1 exit status
$ ./install/bin/arm-none-eabi-readelf -h empty.o
ELF Header:
  Magic:   7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00 
  Class:                             ELF32
  Data:                              2's complement, big endian
  Version:                           1 (current)
  OS/ABI:                            UNIX - System V
  ABI Version:                       0
  Type:                              REL (Relocatable file)
  Machine:                           ARM
  Version:                           0x1
  Entry point address:               0x0
  Start of program headers:          0 (bytes into file)
  Start of section headers:          888 (bytes into file)
  Flags:                             0x5000000, Version5 EABI
  Size of this header:               52 (bytes)
  Size of program headers:           0 (bytes)
  Number of program headers:         0
  Size of section headers:           40 (bytes)
  Number of section headers:         15
  Section header string table index: 12
$ ./install/bin/arm-none-eabi-objdump -f empty.o

empty.o:     file format elf32-bigarm
architecture: armv4t, flags 0x00000010:
HAS_SYMS
start address 0x00000000

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]