From: Andreas Schwab <schwab@suse.de>
To: gcc@gcc.gnu.org
Subject: Re: New Ada build problem on ia64
Date: Wed, 21 Nov 2001 15:29:00 -0000 [thread overview]
Message-ID: <jesnaxwnj1.fsf@sykes.suse.de> (raw)
In-Reply-To: <je1yihy5m0.fsf@sykes.suse.de> (Andreas Schwab's message of "29 Nov 2001 16:11:19 +0100")
Andreas Schwab <schwab@suse.de> writes:
|> There is a new build problem with the Ada compiler on ia64:
|>
|> gcc -c -g -W -Wall -gnatpg -gnata -I- -I. -I../../../gcc/ada ../../../gcc/ada/ali.adb
|> ali.adb:52:27: warning: loop range is null, loop will not execute
|> ali.adb:473:18: warning: loop range is null, loop will not execute
|> ali.adb:637:19: warning: loop range is null, loop will not execute
|> ali.adb:757:27: warning: loop range is null, loop will not execute
|> ali.adb:1040:30: warning: loop range is null, loop will not execute
|>
|> The compiler has been built by a ia32->ia64 cross compiler, using CVS from
|> earlier today.
Update: the problem vanishes if I build the compiler with -O0. I'm now
bootstrapping natively to see whether the problem reappears.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
WARNING: multiple messages have this Message-ID
From: Andreas Schwab <schwab@suse.de>
To: gcc@gcc.gnu.org
Subject: Re: New Ada build problem on ia64
Date: Thu, 29 Nov 2001 08:27:00 -0000 [thread overview]
Message-ID: <jesnaxwnj1.fsf@sykes.suse.de> (raw)
Message-ID: <20011129082700.ePvDHp7YiLR31-Dt_et0VBmbAnVVr3qBRWmYT02y8Bw@z> (raw)
In-Reply-To: <je1yihy5m0.fsf@sykes.suse.de>
Andreas Schwab <schwab@suse.de> writes:
|> There is a new build problem with the Ada compiler on ia64:
|>
|> gcc -c -g -W -Wall -gnatpg -gnata -I- -I. -I../../../gcc/ada ../../../gcc/ada/ali.adb
|> ali.adb:52:27: warning: loop range is null, loop will not execute
|> ali.adb:473:18: warning: loop range is null, loop will not execute
|> ali.adb:637:19: warning: loop range is null, loop will not execute
|> ali.adb:757:27: warning: loop range is null, loop will not execute
|> ali.adb:1040:30: warning: loop range is null, loop will not execute
|>
|> The compiler has been built by a ia32->ia64 cross compiler, using CVS from
|> earlier today.
Update: the problem vanishes if I build the compiler with -O0. I'm now
bootstrapping natively to see whether the problem reappears.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-11-29 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 14:56 Andreas Schwab
2001-11-21 15:29 ` Andreas Schwab [this message]
2001-11-22 0:11 ` Andreas Schwab
2001-11-22 0:18 ` guerby
2001-11-22 0:35 ` Andreas Schwab
2001-11-29 15:01 ` Andreas Schwab
2001-11-29 14:49 ` guerby
2001-11-29 14:21 ` Andreas Schwab
2001-11-29 8:27 ` Andreas Schwab
2001-11-29 7:11 ` Andreas Schwab
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=jesnaxwnj1.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc@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: 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).