From: Richard Guenther <richard.guenther@gmail.com>
To: Toon Moene <toon@moene.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: lto1: internal compiler error: in lto_symtab_merge_decls_1, at lto-symtab.c:549
Date: Sat, 24 Apr 2010 18:11:00 -0000 [thread overview]
Message-ID: <h2s84fc9c001004241107p394ede6cla6289cc4da32e72a@mail.gmail.com> (raw)
In-Reply-To: <4BD2F215.5010704@moene.org>
On Sat, Apr 24, 2010 at 3:28 PM, Toon Moene <toon@moene.org> wrote:
> While compiling our Weather Forecasting code with the latest trunk, I got
> the following (don't know how long this has been a problem, as I haven't
> tried -flto recently):
>
> lto1: internal compiler error: in lto_symtab_merge_decls_1, at
> lto-symtab.c:549
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> lto-wrapper: gfortran returned 1 exit status
> /usr/snp/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../x86_64-unknown-linux-gnu/bin/ld:
> fatal error: lto-wrapper failed
> collect2: ld returned 1 exit status
>
> lto-symtab.c:549:
>
> 524
> 525 /* Helper to process the decl chain for the symbol table entry *SLOT.
> */
> 526
> 527 static int
> 528 lto_symtab_merge_decls_1 (void **slot, void *data ATTRIBUTE_UNUSED)
> ....
> 545 /* Assert it's the only one. */
> 546 if (prevailing)
> 547 for (e = prevailing->next; e; e = e->next)
> 548 gcc_assert (e->resolution != LDPR_PREVAILING_DEF_IRONLY
> 549 && e->resolution != LDPR_PREVAILING_DEF);
>
> Of course, I'd like to make a test case out of this - but what is this
> assert checking ?
It is checking that for one symbol we only have one definition.
You are using -fuse-linker-plugin?
Richard.
> Reducing from several 100's of thousands of lines of
> Fortran might be more difficult than to reason from first principles about
> how this assert might be hit.
>
> Thanks in advance,
>
> --
> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
> At home: http://moene.org/~toon/
> Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html#Fortran
>
next prev parent reply other threads:[~2010-04-24 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 13:48 Toon Moene
2010-04-24 18:11 ` Richard Guenther [this message]
2010-04-25 11:28 ` Toon Moene
2010-04-25 19:34 ` Richard Guenther
2010-04-25 19:49 ` Steven Bosscher
2010-04-25 21:01 ` Richard Guenther
2010-04-25 22:16 ` Dave Korn
2010-04-25 22:21 ` Steven Bosscher
2010-04-26 2:13 ` Dave Korn
2010-04-26 10:00 ` Richard Guenther
[not found] ` <4BD906D5.1010408@gmail.com>
2010-04-29 9:13 ` LTO vs static library archives [was Re: lto1: internal compiler error: in lto_symtab_merge_decls_1, at lto-symtab.c:549] Richard Guenther
2010-04-29 9:21 ` Steven Bosscher
2010-04-29 13:03 ` Richard Guenther
2010-04-29 14:08 ` Jan Hubicka
2010-04-29 15:24 ` Richard Guenther
2010-04-29 16:09 ` Jan Hubicka
2010-04-29 14:27 ` Ian Lance Taylor
2010-05-14 13:34 ` lto1: internal compiler error: in lto_symtab_merge_decls_1, at lto-symtab.c:549 Toon Moene
2010-05-14 13:40 ` Richard Guenther
2010-05-15 9:47 ` Toon Moene
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=h2s84fc9c001004241107p394ede6cla6289cc4da32e72a@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.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).