public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/15627] [3.5 Regression] Sun CC cannot bootstrap GCC
Date: Sun, 27 Jun 2004 15:01:00 -0000 [thread overview]
Message-ID: <20040627135725.12373.qmail@sourceware.org> (raw)
In-Reply-To: <20040524055718.15627.ebotcazou@gcc.gnu.org>
------- Additional Comments From dberlin at dberlin dot org 2004-06-27 13:57 -------
Subject: Re: [3.5 Regression] Sun CC cannot bootstrap
GCC
On Sun, 2004-06-27 at 13:53 +0000, ebotcazou at gcc dot gnu dot org
wrote:
> > Eric, where does Sun CC stop now?
>
> cc -xarch=v9 -erroff -DHAVE_CONFIG_H -I.
> -I/home/eric/cvs/gcc/libbanshee/libcompat -I..
> -I/home/eric/cvs/gcc/libbanshee/libcompat/../engine
> -I/home/eric/cvs/gcc/libbanshee/libcompat/../include -I. -Ddeletes=
> -Dtraditional= -Dsameregion= -Dparentptr= -g -c
> /home/eric/cvs/gcc/libbanshee/libcompat/regions.c
> "/home/eric/cvs/gcc/libbanshee/libcompat/regions.c", line 374: address of a void
> object cannot be taken
> "/home/eric/cvs/gcc/libbanshee/libcompat/regions.c", line 374: address of a void
> object cannot be taken
> cc: acomp failed for /home/eric/cvs/gcc/libbanshee/libcompat/regions.c
> gmake[3]: *** [regions.o] Error 2
>
Can you simply delete that function/ifdef block (findgrefs), and see
what happens next?
The whole find* functions aren't used anywhere by us.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15627
next prev parent reply other threads:[~2004-06-27 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 1:55 [Bug bootstrap/15627] New: " ebotcazou at gcc dot gnu dot org
2004-05-25 6:39 ` [Bug other/15627] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-05-25 8:08 ` cvs-commit at gcc dot gnu dot org
2004-05-25 8:44 ` dberlin at gcc dot gnu dot org
2004-05-31 7:59 ` ebotcazou at gcc dot gnu dot org
2004-05-31 13:13 ` pinskia at gcc dot gnu dot org
2004-06-27 2:45 ` [Bug bootstrap/15627] " giovannibajo at libero dot it
2004-06-27 4:29 ` giovannibajo at libero dot it
2004-06-27 6:49 ` ebotcazou at gcc dot gnu dot org
2004-06-27 11:24 ` cvs-commit at gcc dot gnu dot org
2004-06-27 12:49 ` giovannibajo at libero dot it
2004-06-27 13:57 ` ebotcazou at gcc dot gnu dot org
2004-06-27 15:01 ` dberlin at dberlin dot org [this message]
2004-06-27 15:13 ` giovannibajo at libero dot it
2004-08-18 18:35 ` pinskia at gcc dot gnu dot org
2004-09-10 0:24 ` giovannibajo at libero dot it
2004-09-10 7:09 ` [Bug bootstrap/15627] [4.0 " pinskia at gcc dot gnu dot 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=20040627135725.12373.qmail@sourceware.org \
--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).