public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-17 6:58 giovannibajo
0 siblings, 0 replies; 6+ messages in thread
From: giovannibajo @ 2003-05-17 6:58 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, tausq
Synopsis: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
State-Changed-From-To: open->feedback
State-Changed-By: bajo
State-Changed-When: Sat May 17 06:57:31 2003
State-Changed-Why:
See Dara's question.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9631
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-21 9:14 ehrhardt
0 siblings, 0 replies; 6+ messages in thread
From: ehrhardt @ 2003-05-21 9:14 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, tausq
Synopsis: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
State-Changed-From-To: feedback->open
State-Changed-By: cae
State-Changed-When: Wed May 21 09:14:28 2003
State-Changed-Why:
Submitter reconfirmed this for 3.3.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9631
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-19 1:26 Randolph Chung
0 siblings, 0 replies; 6+ messages in thread
From: Randolph Chung @ 2003-05-19 1:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9631; it has been noted by GNATS.
From: Randolph Chung <randolph@tausq.org>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
Dara Hazeghi <dhazeghi@yahoo.com>
Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
Date: Sun, 18 May 2003 18:27:00 -0700
> Ok. Would you please send us a preprocessed source reproducing the bug
oh, actually here's a very simple test case:
tausq@gsyprf11:~/build/build-3.3/gcc$ cat bug.c
struct SjLj_Function_Context { unsigned data[4]; };
tausq@gsyprf11:~/build/build-3.3/gcc$ ./xgcc -v
Using built-in specs.
Configured with: ../gcc-3.3/configure --enable-languages=c --prefix=/opt/palinux --disable-shared --disable-nls --with-system-zlib --without-included-gettext --enable-debug --host=hppa-linux --build=hppa-linux --target=hppa64-linux --enable-sjlj-exceptions --disable-threads
Thread model: single
gcc version 3.3
tausq@gsyprf11:~/build/build-3.3/gcc$ ./xgcc -B. -c bug.c
bug.c:1: error: size of array `data' is too large
fwiw i see that this message is printed by two places in
grokdeclarator()... adding a printf i see that it's dying in the one at
line 4070.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-19 0:06 Giovanni Bajo
0 siblings, 0 replies; 6+ messages in thread
From: Giovanni Bajo @ 2003-05-19 0:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9631; it has been noted by GNATS.
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Randolph Chung" <randolph@tausq.org>,
<gcc-bugs@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>,
"Dara Hazeghi" <dhazeghi@yahoo.com>
Cc:
Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
Date: Mon, 19 May 2003 02:03:10 +0200
Randolph Chung <randolph@tausq.org> wrote:
> Same thing with gcc-3.3 release:
>
> /home/tausq/build/build-3.3/gcc/xgcc -B/home/tausq/build/build-3.3/gcc/
> -B/opt/palinux/hppa64-linux/bin/ -B/opt/palinux/hppa64-linux/lib/ -isystem
> /opt/palinux/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
./include
> -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
> -Dinhibit_libc -I. -I. -I../../gcc-3.3/gcc -I../../gcc-3.3/gcc/.
> -I../../gcc-3.3/gcc/config -I../../gcc-3.3/gcc/../include -fexceptions -c
> ../../gcc-3.3/gcc/unwind-sjlj.c -o libgcc/./unwind-sjlj.o
> ../../gcc-3.3/gcc/unwind-sjlj.c:56: error: size of array `data' is too
> large
Ok. Would you please send us a preprocessed source reproducing the bug
(basically, just add -E to that line)? You should verify that the preprocess
source still confuse the same stage 1 compiler (build-3.3/gcc/xgcc) and
start cutting down the command line down to the minimum to still get the
error. Let us know that minimal command line as well.
After that, it would help if you could try the same preprocessed file and
the same command line with a fully built GCC on the same platform. Is it
possible to build GCC 3.3 at all on that platform (maybe tweaking the
configure line)? Otherwise, at least try with the newest version of GCC you
can build.
Thanks.
Giovanni Bajo
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-17 17:06 Randolph Chung
0 siblings, 0 replies; 6+ messages in thread
From: Randolph Chung @ 2003-05-17 17:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9631; it has been noted by GNATS.
From: Randolph Chung <randolph@tausq.org>
To: giovannibajo@libero.it, gcc-bugs@gcc.gnu.org,
gcc-gnats@gcc.gnu.org, Dara Hazeghi <dhazeghi@yahoo.com>
Cc:
Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
Date: Sat, 17 May 2003 10:02:08 -0700
In reference to a message from giovannibajo@libero.it, dated May 17:
> Synopsis: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bajo
> State-Changed-When: Sat May 17 06:57:31 2003
> State-Changed-Why:
> See Dara's question.
Same thing with gcc-3.3 release:
/home/tausq/build/build-3.3/gcc/xgcc -B/home/tausq/build/build-3.3/gcc/ -B/opt/palinux/hppa64-linux/bin/ -B/opt/palinux/hppa64-linux/lib/ -isystem /opt/palinux/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc-3.3/gcc -I../../gcc-3.3/gcc/. -I../../gcc-3.3/gcc/config -I../../gcc-3.3/gcc/../include -fexceptions -c ../../gc c-3.3/gcc/unwind-sjlj.c -o libgcc/./unwind-sjlj.o
../../gcc-3.3/gcc/unwind-sjlj.c:56: error: size of array `data' is too large
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
@ 2003-05-17 1:46 Dara Hazeghi
0 siblings, 0 replies; 6+ messages in thread
From: Dara Hazeghi @ 2003-05-17 1:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR bootstrap/9631; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: tausq@debian.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap
Date: Fri, 16 May 2003 18:40:31 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=9631
Hello,
I can't test with a cross compiler here (missing necessary headers),
but would be possible for you to check whether this bug is still
present in gcc 3.3? Thanks,
Dara
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-05-21 9:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-17 6:58 bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap giovannibajo
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 9:14 ehrhardt
2003-05-19 1:26 Randolph Chung
2003-05-19 0:06 Giovanni Bajo
2003-05-17 17:06 Randolph Chung
2003-05-17 1:46 Dara Hazeghi
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).