public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com> To: vmakarov@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/3589: GCC 3.0-CVS illegal instruction on hppa1.1-proelf Date: Tue, 26 Mar 2002 09:56:00 -0000 [thread overview] Message-ID: <20020326175605.26929.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3589; it has been noted by GNATS. From: Vladimir Makarov <vmakarov@redhat.com> To: law@redhat.com Cc: Joel Sherrill <joel.sherrill@OARcorp.com>, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, vmakarov@gcc.gnu.org, joel@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: bootstrap/3589: GCC 3.0-CVS illegal instruction on hppa1.1-proelf Date: Tue, 26 Mar 2002 12:55:26 -0500 law@redhat.com wrote: > > In message <3CA0ADA7.34D73D79@OARcorp.com>, Joel Sherrill writes: > > Could the __PRO__ (or something similar) be part of the cpp predefines > > for this configuration so non-gcc assembly can do the right thing? I > > know that at least libgloss and RTEMS have hppa assembly. > It would be fairly trivial. It could be added to CPP_PREDEFINES in > pa-pro-end.h > > > Of course, this all begs the bigger question... how many embedded hppa > > users are there really? :) > Very very few. The embedded PA consortium basically broke up in the late > 90s and we haven't had customers for these tools since. As a result they > are basically unsupported/bitrotting. Looking to the future, I don't expect > to see embedded PA customers. It just doesn't make sense given the > availability to MIPS, PPC & Arm embedded processors. > > > > 2002-03-26 Vladimir Makarov <vmakarov@redhat.com> > > > > > > * pa/t-pro (TARGET_LIBGCC2_CFLAGS): New macro. > > > > > > * pa/lib2funcs.asm: Don't use .SPACE and .SUBSPACE if __PRO__ is > > > defined. > > > > > > Index: pa/lib2funcs.asm > > > =================================================================== > > > RCS file: /cvs/gcc/gcc/gcc/config/pa/lib2funcs.asm,v > > > retrieving revision 1.6 > > > diff -c -p -r1.6 lib2funcs.asm > > > *** lib2funcs.asm 2001/04/16 18:30:45 1.6 > > > --- lib2funcs.asm 2002/03/26 16:57:10 > > > *************** > > > *** 28,33 **** > > > --- 28,34 ---- > > > ; the Free Software Foundation, 59 Temple Place - Suite 330, > > > ; Boston, MA 02111-1307, USA. > > > > > > + #ifndef __PRO__ > > > .SPACE $PRIVATE$ > > > .SUBSPA $DATA$,QUAD=1,ALIGN=8,ACCESS=31 > > > .SUBSPA $BSS$,QUAD=1,ALIGN=8,ACCESS=31,ZERO,SORT=82 > > > *************** > > > *** 35,45 **** > > > .SUBSPA $LIT$,QUAD=0,ALIGN=8,ACCESS=44 > > > .SUBSPA $CODE$,QUAD=0,ALIGN=8,ACCESS=44,CODE_ONLY > > > .SUBSPA $MILLICODE$,QUAD=0,ALIGN=8,ACCESS=44,SORT=8 > > > ! > > > .IMPORT $$dyncall,MILLICODE > > > .SPACE $TEXT$ > > > .SUBSPA $CODE$ > > > ! > > > ; Simply call with the address of the desired import stub in %r22 and > > > ; arguments in the normal place (%r26-%r23 and stack slots). > > > ; > > > --- 36,49 ---- > > > .SUBSPA $LIT$,QUAD=0,ALIGN=8,ACCESS=44 > > > .SUBSPA $CODE$,QUAD=0,ALIGN=8,ACCESS=44,CODE_ONLY > > > .SUBSPA $MILLICODE$,QUAD=0,ALIGN=8,ACCESS=44,SORT=8 > > > ! #endif > > > .IMPORT $$dyncall,MILLICODE > > > + #ifndef __PRO__ > > > .SPACE $TEXT$ > > > .SUBSPA $CODE$ > > > ! #else > > > ! .text > > > ! #endif > > > ; Simply call with the address of the desired import stub in %r22 and > > > ; arguments in the normal place (%r26-%r23 and stack slots). > > > ; > > > Index: pa/t-pro > > > =================================================================== > > > RCS file: /cvs/gcc/gcc/gcc/config/pa/t-pro,v > > > retrieving revision 1.8 > > > diff -c -p -r1.8 t-pro > > > *** t-pro 2002/02/16 22:30:35 1.8 > > > --- t-pro 2002/03/26 16:57:10 > > > *************** T_ADAFLAGS=-mdisable-indexing > > > *** 2,7 **** > > > --- 2,11 ---- > > > > > > LIB2FUNCS_EXTRA=lib2funcs.asm > > > > > > + # The following macro definition is used to switch off usage of .SPACE > > > + # and .SUBSPACE pseudo-ops in lib2funcs.asm for elf targets. > > > + TARGET_LIBGCC2_CFLAGS=-D__PRO__ > > > + > > > # We want fine grained libraries, so use the new code to build the > > > # floating point emulation libraries. > > > FPBIT = fp-bit.c > > > > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc > > &pr=3589 > Vlad can you move the -D__PRO__ into the CPP_PREDEFINES in pa-pro-end.h? Ok, I'll rewrite the patch and resend it again. Vlad
next reply other threads:[~2002-03-26 17:56 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-26 9:56 Vladimir Makarov [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-24 9:11 joel 2002-04-01 14:54 vmakarov 2002-03-28 13:46 John David Anglin 2002-03-28 12:56 Vladimir Makarov 2002-03-27 10:56 Vladimir Makarov 2002-03-26 20:06 law 2002-03-26 14:26 Joel Sherrill 2002-03-26 14:26 Vladimir Makarov 2002-03-26 13:36 Joel Sherrill 2002-03-26 13:16 Vladimir Makarov 2002-03-26 13:06 Joel Sherrill 2002-03-26 12:56 Vladimir Makarov 2002-03-26 10:16 Joel Sherrill 2002-03-26 9:56 law 2002-03-26 9:36 Vladimir Makarov 2002-03-26 9:26 Joel Sherrill 2002-03-26 9:16 Vladimir Makarov 2002-03-26 6:26 Joel Sherrill 2002-03-25 10:26 Vladimir Makarov 2002-03-25 10:16 law 2002-03-25 8:26 Vladimir Makarov 2002-03-22 9:41 vmakarov 2001-07-06 6:46 joel
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=20020326175605.26929.qmail@sources.redhat.com \ --to=vmakarov@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=vmakarov@gcc.gnu.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: linkBe 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).