From: Arnaud Lacombe <lacombar@gmail.com>
To: binutils@sourceware.org
Subject: [x86] gas error: can't extend frag 2134796 chars
Date: Fri, 29 Jul 2011 16:25:00 -0000 [thread overview]
Message-ID: <CACqU3MW5V_-80Z048j88q2BgcNBXWuxBxsP7uqbxu+4CjcUQow@mail.gmail.com> (raw)
Hi,
It seems there is a regression in GAS x86-64. The following:
# 1 "arch/x86/boot/compressed/piggy.S"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "./include/generated/autoconf.h" 1
# 1 "<command-line>" 2
# 1 "arch/x86/boot/compressed/piggy.S"
.section ".rodata..compressed","a",@progbits
.globl z_input_len
z_input_len = 2134796
.globl z_output_len
z_output_len = 5716952
.globl z_extract_offset
z_extract_offset = 0x37b000
.globl z_extract_offset_negative
z_extract_offset_negative = -0x37b000
.globl input_data, input_data_end
input_data:
.incbin "zero"
input_data_end:
with `zero' being:
% dd if=/dev/zero of=zero count=1 bs=2134796
triggers:
% /src/x86-64/obj/destdir/lib/gcc/x86_64-none-linux/4.7.0/../../../../x86_64-none-linux/bin/as
--32 -o piggy.o piggy.s
GNU assembler version 2.21.53 (x86_64-none-linux) using BFD version
(GNU Binutils) 2.21.53.20110726
arch/x86/boot/compressed/piggy.S: Assembler messages:
arch/x86/boot/compressed/piggy.S:12: Fatal error: can't extend frag
2134796 chars
While the system assembler is fine:
% as -v --32 -o piggy.o piggy.s
GNU assembler version 2.20.51.0.7 (x86_64-redhat-linux) using BFD
version version 2.20.51.0.7-8.fc14 20100318
- Arnaud
next reply other threads:[~2011-07-29 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 16:25 Arnaud Lacombe [this message]
2011-07-29 17:02 ` H.J. Lu
2011-07-29 17:30 ` Arnaud Lacombe
2011-07-29 17:40 ` H.J. Lu
2011-07-29 22:47 ` Arnaud Lacombe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACqU3MW5V_-80Z048j88q2BgcNBXWuxBxsP7uqbxu+4CjcUQow@mail.gmail.com \
--to=lacombar@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).