From: Alan Modra <amodra@bigpond.net.au>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: binutils@sourceware.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@osdl.org>,
Gerd Hoffmann <kraxel@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Chuck Ebbert <76306.1226@compuserve.com>,
binutils@sources.redhat.com
Subject: Re: as bug (was: Re: smp/up alternatives crash when CONFIG_HOTPLUG_CPU)
Date: Sat, 6 May 2006 12:41:41 +0930 [thread overview]
Message-ID: <20060506031140.GE11597@bubble.grove.modra.org> (raw)
In-Reply-To: <200605051613.24704.vda@ilport.com.ua>
On Fri, May 05, 2006 at 04:13:24PM +0300, Denis Vlasenko wrote:
> On Friday 05 May 2006 15:20, Alan Modra wrote:
> > the frag base addresses have not yet been set, and zero is used. ie.
> > gas tries to assemble ".fill -5,1,0x42".
The fact that enabling gas listings fixes this has been nagging at me
since writing the sketchy description of gas frags and relaxation.
I'd forgotten that relaxation keeps iterating over all sections until no
frag changes address. ie. even though the first .fill is using invalid
addresses, there will be a subsequent pass that uses the correct value.
The reason why gas -al helps with this case is that gas creates a new
frag for each line as somewhere to hang the file/line number info. So
both "661" and "662" start off at offset zero in their frags and the
initial pass .fill has a zero length rather than a negative one.
So perhaps gas ought to be able to handle this after all.. I'll see if
I can come up with a fix.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
prev parent reply other threads:[~2006-05-06 3:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 9:46 smp/up alternatives crash when CONFIG_HOTPLUG_CPU Ingo Molnar
2006-04-20 5:29 ` Ingo Molnar
2006-04-20 7:45 ` Andi Kleen
2006-04-20 15:14 ` Linus Torvalds
2006-04-20 15:26 ` Ingo Molnar
2006-04-21 7:48 ` Ingo Molnar
2006-05-05 8:40 ` as bug (was: Re: smp/up alternatives crash when CONFIG_HOTPLUG_CPU) Denis Vlasenko
2006-05-05 8:45 ` Denis Vlasenko
2006-05-05 12:20 ` Alan Modra
2006-05-05 13:13 ` Denis Vlasenko
2006-05-06 3:11 ` Alan Modra [this message]
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=20060506031140.GE11597@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
--cc=vda@ilport.com.ua \
/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
Powered by JetHome