From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc problems
Date: Fri, 06 Feb 2004 11:46:34 +0000 [thread overview]
Message-ID: <jeisiksa5h.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040206000058.7e928d80.akpm@osdl.org>
Jim Wilson <wilson@specifixinc.com> writes:
> On Fri, 2004-02-06 at 00:00, Andrew Morton wrote:
>> ../../gcc-3.4-cvs/gcc/config/ia64/unwind-ia64.c: In function `uw_frame_state_for':
>> ../../gcc-3.4-cvs/gcc/config/ia64/unwind-ia64.c:1779: error: structure has no member named `sc_rbs_base'
>> ../../gcc-3.4-cvs/gcc/config/ia64/unwind-ia64.c:1779: error: structure has no member named `sc_loadrs'
>
> This is from the MD_FALLBACK_FRAME_STATE_FOR macro in
> gcc/config/ia64/linux.h, which handles machine and OS dependent
> unwinding from signal handers. It uses signal.h and sys/context.h.
> These are things that could have perhaps changed with a new kernel or
> glibc. If the signal context structure has changed, then we need a new
> version of this code, and will somehow have to choose the right one.
The fields were named differently in old versions of glibc, but the whole
layout didn't change in any way.
- unsigned long int sc_rsvd[16];/* reserved for future use */
+ unsigned long int sc_rbs_base;/* NULL or new base of sighandler's rbs */
+ unsigned long int sc_loadrs; /* see description above */
+ unsigned long int sc_ar25; /* cmp8xchg16 uses this */
+ unsigned long int sc_ar26; /* rsvd for scratch use */
+ unsigned long int sc_rsvd[12];/* reserved for future use */
> The easiest workaround is probably to install libunwind on your system
The right fix is not to use a 2 years old glibc.
revision 1.7
date: 2001/10/01 00:04:10; author: drepper; state: Exp; lines: +3 -1
(struct sigcontext): Add sc_loadrs and sc_rbs_bas to match current kernel.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-02-06 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 8:00 gcc problems Andrew Morton
2004-02-06 8:37 ` Ian Wienand
2004-02-06 8:43 ` Andrew Morton
2004-02-06 9:49 ` Jim Wilson
2004-02-06 11:46 ` Andreas Schwab [this message]
2004-02-06 16:30 ` Andrew Morton
2004-02-06 16:50 ` Dan Kegel
2004-02-06 17:34 ` Wichmann, Mats D
2004-02-07 2:05 ` Jim Wilson
2004-02-07 5:49 ` Andrew Morton
2004-02-10 7:37 ` 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=jeisiksa5h.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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