From: "H. J. Lu" <hjl@lucon.org>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Andreas Schwab <schwab@suse.de>, gcc@gcc.gnu.org
Subject: Re: Gcc mainline failed to bootstrap on Linux/ia64
Date: Tue, 09 Sep 2003 06:28:00 -0000 [thread overview]
Message-ID: <20030909052132.GA4617@lucon.org> (raw)
In-Reply-To: <20030909000521.GM12333@atrey.karlin.mff.cuni.cz>
On Tue, Sep 09, 2003 at 02:05:21AM +0200, Jan Hubicka wrote:
> > Jan Hubicka <hubicka@ucw.cz> writes:
> >
> > >> Gcc mainline on Sat Sep 6 07:08:21 PDT 2003 failed to bootstrap on
> > >> Linux/ia64. I got
> > >>
> > >> In file included from /net/gnu/export/gnu/src/gcc/gcc/libjava/include/jvm.h:23,
> > >> from /net/gnu/export/gnu/src/gcc/gcc/libjava/exception.cc:22:
> > >> ./include/java-threads.h:228: internal compiler error: Segmentation fault
> > >> Please submit a full bug report,
> > >> with preprocessed source if appropriate.
> > >> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> > >
> > > This appears to be related to change of mine to notice_global_symbol.
> > > I just commited fix to different problem that may fix it. Can you
> > > please ensure that the following patch is in your tree?
> > > * cgraph.c (cgraph_mark_reachable_node): Only enqueue finalized functions.
> > > (cgraph_varpool_finalize_decl): Notice global symbol when needed.
> >
> > This is still not fixed.
> >
>
> The problem obviously is that we see global variable placed in register.
> I am quite surprised to see this in java, but the attached patch should
> help. Can you, please try it out?
> Sorry for the delay - bit too many problems to deal with at once :(
>
> Tue Sep 9 02:03:42 CEST 2003 Jan Hubicka <jh@suse.cz>
> * varasm.c (notice_global_symbol): Fix dealing with registers.
> Index: varasm.c
> ===================================================================
> RCS file: /cvs/gcc/gcc/gcc/varasm.c,v
> retrieving revision 1.381
> diff -c -3 -p -r1.381 varasm.c
> *** varasm.c 5 Sep 2003 04:24:26 -0000 1.381
> --- varasm.c 9 Sep 2003 00:03:31 -0000
> *************** notice_global_symbol (tree decl)
> *** 1058,1063 ****
> --- 1058,1066 ----
> char *name;
> rtx decl_rtl = DECL_RTL (decl);
>
> + if (GET_CODE (decl_rtl) == REG)
> + return;
> +
> p = (* targetm.strip_name_encoding) (XSTR (XEXP (decl_rtl, 0), 0));
> name = xstrdup (p);
>
I can bootstrap gcc mainline with this patch on Linux/ia64 now. But I
got new failures:
+FAIL: gcc.c-torture/compile/20000120-2.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-2.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-2.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-2.c (test for excess errors)
+FAIL: gcc.c-torture/compile/20011119-2.c (test for excess errors)
+FAIL: gcc.dg/debug/20010207-1.c (test for excess errors)
+FAIL: gcc.dg/debug/20010207-1.c (test for excess errors)
+FAIL: gcc.dg/debug/20010207-1.c (test for excess errors)
+FAIL: g++.dg/init/array11.C (test for excess errors)
+FAIL: libffi.call/closure_fn0.c output pattern test, is 1 2 3 4 127 429 7 8 0
10 11 97 13 19 21 1 3: 756
+FAIL: libffi.call/closure_fn1.c output pattern test, is 1 2 3 4 127 5 6 8 0 10
11 0 13 19 21 1 3: 234
+FAIL: libffi.call/closure_fn2.c output pattern test, is 1 2 3 4 127 5 6 8 0 10
11 0 13 0 21 1 3: 215
+FAIL: libffi.call/closure_fn3.c output pattern test, is 1 2 3 4 5 6 7 8 9 10 0
0 13 0 0 1 3: 72
+FAIL: libffi.call/cls_1_1byte.c execution test
+FAIL: libffi.call/cls_12byte.c execution test
+FAIL: libffi.call/cls_16byte.c execution test
+FAIL: libffi.call/cls_20byte.c execution test
+FAIL: libffi.call/cls_24byte.c execution test
+FAIL: libffi.call/cls_2byte.c execution test
+FAIL: libffi.call/cls_3_1byte.c execution test
+FAIL: libffi.call/cls_3byte1.c execution test
+FAIL: libffi.call/cls_3byte2.c execution test
+FAIL: libffi.call/cls_4_1byte.c execution test
+FAIL: libffi.call/cls_4byte.c execution test
+FAIL: libffi.call/cls_5byte.c execution test
+FAIL: libffi.call/cls_6byte.c execution test
+FAIL: libffi.call/cls_7byte.c execution test
+FAIL: libffi.call/cls_8byte.c execution test
+FAIL: libffi.call/float2.c execution test
+FAIL: libffi.call/float.c execution test
+FAIL: libffi.call/nested_struct1.c execution test
+FAIL: libffi.call/nested_struct.c execution test
+FAIL: libffi.call/problem1.c execution test
+FAIL: libffi.call/pyobjc-tc.c execution test
+FAIL: libffi.call/struct8.c execution test
+FAIL: libffi.special/unwindtest.cc execution test
comparing against 20030903.
H.J.
next prev parent reply other threads:[~2003-09-09 5:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 23:30 H. J. Lu
2003-09-06 23:39 ` Jan Hubicka
2003-09-07 10:38 ` H. J. Lu
2003-09-07 13:52 ` Jan Hubicka
2003-09-07 15:44 ` H. J. Lu
2003-09-07 15:54 ` Andreas Tobler
2003-09-07 16:35 ` Jan Hubicka
2003-09-07 16:39 ` Gabriel Dos Reis
2003-09-07 16:57 ` Kaveh R. Ghazi
2003-09-07 17:12 ` Andreas Tobler
2003-09-07 18:49 ` Andreas Tobler
2003-09-07 20:21 ` Andreas Tobler
2003-09-07 20:22 ` Jan Hubicka
2003-09-08 23:37 ` H. J. Lu
2003-09-09 0:05 ` Jan Hubicka
2003-09-08 23:35 ` H. J. Lu
2003-09-08 14:09 ` Andreas Schwab
2003-09-09 0:20 ` Jan Hubicka
2003-09-09 6:28 ` H. J. Lu [this message]
2003-09-09 10:36 ` Eric Christopher
2003-09-09 13:44 ` Jan Hubicka
2003-09-09 13:41 ` Jan Hubicka
2003-09-09 16:40 ` David Edelsohn
2003-09-09 16:43 ` 20011119-1.c failure (Re: Gcc mainline failed to bootstrap on Linux/ia64) Jan Hubicka
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=20030909052132.GA4617@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=schwab@suse.de \
/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).