From: Steve Ellcey <sje@cup.hp.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Tristan Gingold <gingold@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Douglas Rupp <rupp@gnat.com>
Subject: Re: CFT: Move unwinder to toplevel libgcc
Date: Thu, 07 Jul 2011 22:55:00 -0000 [thread overview]
Message-ID: <1310078773.10986.2627.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <1310058332.10986.2616.camel@hpsje.cup.hp.com>
On Thu, 2011-07-07 at 10:05 -0700, Steve Ellcey wrote:
> On Thu, 2011-07-07 at 15:08 +0200, Rainer Orth wrote:
>
> > In that case, perhaps Steve could have a look? I'd finally like to make
> > some progress on this patch.
> >
> > Thanks.
> > Rainer
>
> When doing an IA64 Linux build (where I do need to compile
> unwind-ia64.c) I am dying with this failure:
>
> In file included from /test/big-foot1/gcc/nightly/src/trunk/libgcc/config/ia64/unwind-ia64.c:35:0:
> ./md-unwind-support.h:42:7: error: unknown type name '_Unwind_FrameState'
> ./md-unwind-support.h:132:54: error: unknown type name '_Unwind_FrameState'
> /test/big-foot1/gcc/nightly/src/trunk/libgcc/config/ia64/unwind-ia64.c: In function 'uw_update_reg_address':
> /test/big-foot1/gcc/nightly/src/trunk/libgcc/config/ia64/unwind-ia64.c:1931:11: warning: cast discards '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
> make[3]: *** [unwind-ia64.o] Error 1
> make[3]: Leaving directory `/test/big-foot1/gcc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/ia64-debian-linux-gnu/libgcc'
> make[2]: *** [all-stage1-target-libgcc] Error 2
>
> Steve Ellcey
> sje@cup.hp.com
It looks like this is caused by having two '#include "md-unwind-support.h"'
lines in unwind-ia64.c. If I remove the first one (mixed in with the other
includes at the top of the file) and leave the second one then the file
compiles. I still get the warning about discarding the cast but I guess that
is OK. I have a bootstrap running on IA64 Linux and it looks good so far.
I haven't had a chance to follow-up on IA64 HP-UX.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2011-07-07 22:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 12:44 [build] " Rainer Orth
2011-06-20 15:21 ` Joseph S. Myers
2011-06-20 15:23 ` Rainer Orth
2011-06-20 15:37 ` Joseph S. Myers
2011-06-20 15:47 ` Rainer Orth
2011-07-04 18:10 ` CFT: " Rainer Orth
2011-07-05 9:35 ` Tristan Gingold
2011-07-07 13:11 ` Rainer Orth
2011-07-07 15:53 ` Steve Ellcey
2011-07-08 18:16 ` Rainer Orth
2011-07-07 16:48 ` Steve Ellcey
2011-07-08 18:24 ` Rainer Orth
2011-07-07 17:08 ` Steve Ellcey
2011-07-07 22:55 ` Steve Ellcey [this message]
2011-07-08 18:55 ` Rainer Orth
2011-07-08 20:18 ` Steve Ellcey
2011-07-12 17:24 ` Steve Ellcey
2011-07-12 17:40 ` Rainer Orth
2011-07-12 17:42 ` Steve Ellcey
2011-07-14 1:47 ` Steve Ellcey
2011-07-15 9:38 ` Rainer Orth
2011-07-18 12:07 ` Rainer Orth
2011-07-18 17:50 ` Steve Ellcey
2011-07-19 11:43 ` Rainer Orth
2011-07-20 23:03 ` Steve Ellcey
2011-07-22 15:36 ` Rainer Orth
2011-07-22 18:56 ` Steve Ellcey
2011-07-22 19:03 ` Rainer Orth
2011-07-22 22:20 ` Steve Ellcey
2011-07-25 17:07 ` Rainer Orth
2011-06-29 10:05 ` [build] " Paolo Bonzini
2011-06-29 10:06 ` Rainer Orth
2011-06-29 11:29 ` Joseph S. Myers
2011-06-29 11:33 ` Paolo Bonzini
2011-06-29 12:40 ` Rainer Orth
2011-06-29 12:17 ` Rainer Orth
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=1310078773.10986.2627.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=rupp@gnat.com \
/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).