public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/52178] [4.7 regression] Ada bootstrap failure in LTO mode
Date: Mon, 13 Feb 2012 17:07:00 -0000 [thread overview]
Message-ID: <bug-52178-4-t8sAjgTFZW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52178-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52178
--- Comment #21 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-02-13 17:06:44 UTC ---
> Yeah. I'm now getting further with Ada LTO bootstrap, but hit an ICE
> during optimization:
>
> /space/rguenther/src/svn/trunk/gcc/ada/sem_prag.adb: In function
> 'sem_prag__analyze_pragma':
> /space/rguenther/src/svn/trunk/gcc/ada/sem_prag.adb:383:0: internal compiler
> error: in forward_edge_to_pdom, at tree-ssa-dce.c:1153
> Please submit a full bug report,
> with preprocessed source if appropriate.
OK, thanks, will debug this one.
> when built with --disable-werror, otherwise I'd see errors with warnings like
>
> ada/b_gnat1.adb:196:7: warning: type of 'locking_policy' does not match
> original declaration [enabled by default]
> In file included from /usr/include/unistd.h:563:0,
> from /space/rguenther/src/svn/trunk/gcc/ada/cstreams.c:268,
> from /usr/include/stdio.h:188,
> from <built-in>:10,
> from <built-in>:5,
> from <built-in>:78,
> from :9:
> /space/rguenther/src/svn/trunk/gcc/ada/init.c:96:7: note: previously declared
> here
> In file included from :101:0:
>
> The warning appears if the middle-end would not consider the types
> compatible and thus would, for example, assign different alias-sets
> when accessing the decl from the different modules.
-Werror is supposed to have been disabled at link time for Ada though
next prev parent reply other threads:[~2012-02-13 17:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 21:37 [Bug lto/52178] New: " ebotcazou at gcc dot gnu.org
2012-02-10 15:10 ` [Bug lto/52178] " rguenth at gcc dot gnu.org
2012-02-10 17:51 ` ebotcazou at gcc dot gnu.org
2012-02-13 11:35 ` rguenth at gcc dot gnu.org
2012-02-13 11:54 ` ebotcazou at gcc dot gnu.org
2012-02-13 11:58 ` rguenther at suse dot de
2012-02-13 12:18 ` ebotcazou at gcc dot gnu.org
2012-02-13 12:29 ` rguenther at suse dot de
2012-02-13 12:39 ` ebotcazou at gcc dot gnu.org
2012-02-13 13:29 ` rguenth at gcc dot gnu.org
2012-02-13 13:43 ` rguenth at gcc dot gnu.org
2012-02-13 13:45 ` rguenth at gcc dot gnu.org
2012-02-13 13:53 ` ebotcazou at gcc dot gnu.org
2012-02-13 13:54 ` ebotcazou at gcc dot gnu.org
2012-02-13 13:56 ` ebotcazou at gcc dot gnu.org
2012-02-13 14:04 ` rguenther at suse dot de
2012-02-13 14:13 ` ebotcazou at gcc dot gnu.org
2012-02-13 14:14 ` rguenther at suse dot de
2012-02-13 14:19 ` rguenther at suse dot de
2012-02-13 14:22 ` ebotcazou at gcc dot gnu.org
2012-02-13 14:44 ` rguenth at gcc dot gnu.org
2012-02-13 17:07 ` ebotcazou at gcc dot gnu.org [this message]
2012-02-14 8:41 ` rguenth at gcc dot gnu.org
2012-02-15 0:11 ` ebotcazou at gcc dot gnu.org
2012-02-15 0:12 ` ebotcazou at gcc dot gnu.org
2012-05-25 20:28 ` ebotcazou at gcc dot gnu.org
2012-05-25 20:30 ` ebotcazou at gcc dot gnu.org
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=bug-52178-4-t8sAjgTFZW@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).