public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Laurent GUERBY" <laurent@guerby.net>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Ada mainline
Date: Thu, 09 Sep 2004 11:51:00 -0000	[thread overview]
Message-ID: <097301c4965a$741c6ee0$2fb82997@bagio> (raw)
In-Reply-To: <1094726493.12757.581.camel@pc.site>

Laurent GUERBY wrote:

> stage1/xgcc -Bstage1/
>  -B/home/guerby/work/gcc/install/install-20040909T003617/i686-pc-linux-gnu/bi
n/
> -c -g -O2      -gnatpg -gnata -g -O1 -fno-inline \ -I- -I. -Iada
> -I/home/guerby/work/gcc/version-head/gcc/ada
> /home/guerby/work/gcc/version-head/gcc/ada/a-except.adb -o
> ada/a-except.o +===========================GNAT BUG
> DETECTED==============================+
>> 3.5.0 20040908 (experimental) (i686-pc-linux-gnu) GCC error:
>> |
>> in peel_address, at tree-ssa-loop-ivopts.c:2560
>> |
>> Error detected at a-exexda.adb:312:8
>> |

This is bcause peel_address does not handle some trees generated by Ada (I
think it was VIEW_CONVERT_EXPR, but I may be wrong). Honza was working on it,
but then he preferred to wait for Zdenek to be back. Bootstrapping
with -fno-ivopts should be a workaround for now.


> ../../xgcc -B../../ -c -g -O2 -fPIC      -W -Wall -gnatpg
> a-nllcef.ads -o a-nllcef.o +===========================GNAT BUG
> DETECTED==============================+
>> 3.5.0 20040908 (experimental) (x86_64-unknown-linux-gnu) GCC error:
>> |
>> in optimize_mode_switching, at lcm.c:1225
>> |
>> Error detected at a-ngcefu.adb:710:1 [a-nllcef.ads:19:1]
>> |

This is PR 17345. It was broken by Uros i387 patch, and Honza has a proposed
solution. See the audit trail for more infos. You may want to double-check that
the attacched patch does indeed cure the Ada failure as well.

Giovanni Bajo


  reply	other threads:[~2004-09-09 10:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 11:37 Laurent GUERBY
2004-09-09 11:51 ` Giovanni Bajo [this message]
2004-09-09 12:06 Richard Kenner
2004-09-09 12:54 ` Arnaud Charlet
2004-09-09 13:13   ` Jan Hubicka
2004-09-09 13:36     ` Arnaud Charlet
2004-09-09 13:43       ` Jan Hubicka
2004-09-09 13:47       ` Paolo Bonzini
2004-09-09 13:48         ` Paolo Bonzini
2004-09-09 13:50         ` Arnaud Charlet
2004-09-09 14:05           ` Arnaud Charlet
2004-09-09 14:03       ` Diego Novillo
2004-09-09 14:51         ` Arnaud Charlet
2004-09-09 18:50           ` Richard Henderson
2004-09-09 19:22 Richard Kenner
2004-09-09 21:00 ` Daniel Berlin
2004-09-09 21:18   ` Robert Dewar
2004-09-09 21:22     ` Diego Novillo
2004-09-09 21:39       ` Joseph S. Myers
2004-09-09 21:52       ` Robert Dewar
2004-09-09 22:15         ` Richard Henderson
2004-09-09 22:38         ` Diego Novillo
2004-09-09 23:00           ` Robert Dewar
2004-09-09 22:41         ` Gabriel Dos Reis
2004-09-09 23:06           ` Robert Dewar
     [not found]         ` <4140D9D6.504@bellsouth.net>
2004-09-09 22:57           ` Robert Dewar
2004-09-09 23:11             ` Robert Dewar
2004-09-09 23:14             ` Richard Henderson
2004-09-09 23:19               ` Robert Dewar
2004-09-10 11:27                 ` Laurent GUERBY
2004-09-09 21:54       ` Robert Dewar
2004-09-09 23:31         ` Kaveh R. Ghazi
2004-09-10 15:55           ` Manfred Hollstein
2004-09-09 21:29     ` Daniel Berlin
2004-09-09 21:57       ` Robert Dewar
2004-09-09 22:32         ` Diego Novillo
2004-09-09 22:37 D. Starner
2004-09-09 22:53 ` Robert Dewar
2004-09-10  0:38   ` Florian Weimer
2004-09-10 15:02 ` Paul Koning
2004-09-10 17:40   ` Matt Austern
2004-09-10  1:59 Richard Kenner
2004-09-10  8:45 ` Robert Dewar
2004-09-10  9:50 ` Joseph S. Myers
2004-09-10 15:40 ` James A. Morrison
2004-09-10 12:34 Richard Kenner
2004-09-10 14:50 ` Gabriel Dos Reis

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='097301c4965a$741c6ee0$2fb82997@bagio' \
    --to=giovannibajo@libero.it \
    --cc=gcc@gcc.gnu.org \
    --cc=laurent@guerby.net \
    /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).