public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/6669: Irix6.5 ada bootstrap fail in ada/targparm.adb Date: Wed, 15 May 2002 19:36:00 -0000 [thread overview] Message-ID: <20020516023601.2666.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/6669; it has been noted by GNATS. From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: David.Billinghurst@riotinto.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: ada/6669: Irix6.5 ada bootstrap fail in ada/targparm.adb Date: Thu, 16 May 2002 04:29:55 +0200 (MEST) David.Billinghurst@riotinto.com writes: > gcc -c -g -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -gnatpg -gnata -I- -I. -I/exd4/billingd/src/gcc/gcc/ada /exd4/billingd/src/gcc/gcc/ada/targparm.adb > as: Error: /var/tmp/cca4KkNE.s, line 5416: value must be -128..255 > .byte 0x80000000 > as: Error: /var/tmp/cca4KkNE.s, line 5417: value must be -128..255 > .byte 0x80000003 > as: Error: /var/tmp/cca4KkNE.s, line 5536: value must be -128..255 > .byte 0x80000000 > as: Error: /var/tmp/cca4KkNE.s, line 5537: value must be -128..255 > .byte 0x80000014 > as: Error: /var/tmp/cca4KkNE.s, line 5656: value must be -128..255 > .byte 0x80000000 > and so on > > The bootstrap compiler was a mips-sgi-irix6.2 build of > gnat-3.13p supplied by rainer orth - see PR ada/6552. This only happens on the mainline, the 3.1 branch is fine. Here's what's going on: targparm.adb is compiled using the .adb.o suffix rule, which uses $(ALL_ADAFLAGS), among others. This variable differs between 3.1 and 3.2: The 3.1 gcc/ada/Makefile has ALL_ADAFLAGS = $(ADA_CFLAGS) $(X_ADAFLAGS) $(T_ADAFLAGS) $(ADAFLAGS) ADA_CFLAGS = whereas on the mainline this is ALL_ADAFLAGS = $(CFLAGS) $(ALL_ADA_CFLAGS) $(X_ADAFLAGS) $(T_ADAFLAGS) \ $(ADAFLAGS) CFLAGS = -g ALL_ADA_CFLAGS = $(X_ADA_CFLAGS) $(T_ADA_CFLAGS) $(ADA_CFLAGS) I.e. the mainline adds -g, which breaks assembly. This is obviously a bug in the bootstrap gnat. Unfortunately, due to PR ada/6552 one cannot currently build a complete 3.1 based gnat, so removing -g on the mainline (probably stage1 only) is the only option until this is fixed. Rainer
next reply other threads:[~2002-05-16 2:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-15 19:36 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:31 giovannibajo 2003-05-12 16:06 Rainer Orth 2003-05-12 11:15 giovannibajo 2003-05-10 21:46 Dara Hazeghi 2002-05-15 20:06 Billinghurst, David (CRTS) 2002-05-15 19:06 David.Billinghurst
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=20020516023601.2666.qmail@sources.redhat.com \ --to=ro@techfak.uni-bielefeld.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).