From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: heads up: apparent GAS bug in current (CVS) binutils
Date: Thu, 12 May 2005 21:55:40 +0000 [thread overview]
Message-ID: <200505122155.j4CLteGX024882@napali.hpl.hp.com> (raw)
Just a quick heads up (it's late here and I'll be on travel tomorrow
so I don't have time for a proper investigation/bug-report at the
moment):
If I build the kernel with the assembler from the current CVS
binutils, I see these errors:
ERROR: proc_set_irq_affinity: 179742 slots, total region length = 36
ERROR: idle_regs: 68847 slots, total region length = 15
The error in proc_set_irq_affinity() is definitely real and a result
of the assembler (the assembly code generated by GCC looks fine). I
didn't check on idle_regs.
readelf -u vmlinux shows this:
<proc_set_irq_affinity>: [0xa00000010000ef60-0xa0000001000f9000], info at +0x765
c50
v1, flags=0x0 (), len=8 bytes
R2:prologue_gr(mask=[rp,ar.pfs],grsave=r34,rlen=8)
P7:pfs_when(t=0)
P7:rp_when(t=7)
R1:body(rlen()
<move_irq>: [0xa00000010000f0c0-0xa00000010000f250], info at +0x75da00
Note how the end-address of proc_set_irq_affinity() is _way_ beyond
the start-address of the next function, move_irq. Clearly something
weird happened here.
If I use the standard Debian/sarge assembler, these errors go away and
the unwind-info looks sane.
--david
next reply other threads:[~2005-05-12 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 21:55 David Mosberger [this message]
2005-05-13 17:32 ` heads up: apparent GAS bug in current (CVS) binutils Lu, Hongjiu
2005-05-13 17:44 ` Lu, Hongjiu
2005-05-13 18:48 ` Lu, Hongjiu
2005-05-13 20:34 ` David Mosberger
2005-05-13 20:50 ` H. J. Lu
2005-05-13 20:59 ` David Mosberger
2005-05-13 21:01 ` H. J. Lu
2005-05-13 21:05 ` David Mosberger
2005-05-17 20:48 ` Luck, Tony
2005-05-17 20:53 ` David Mosberger
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=200505122155.j4CLteGX024882@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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