This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/41069] lto1: error: type mismatch in indirect reference
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Aug 2009 09:05:34 -0000
- Subject: [Bug middle-end/41069] lto1: error: type mismatch in indirect reference
- References: <bug-41069-6642@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #17 from rguenther at suse dot de 2009-08-17 09:05 -------
Subject: Re: lto1: error: type mismatch in indirect
reference
On Mon, 17 Aug 2009, jv244 at cam dot ac dot uk wrote:
> ------- Comment #16 from jv244 at cam dot ac dot uk 2009-08-17 07:39 -------
> (In reply to comment #15)
>
> > > > > -flto needs about 35min compile time and 10.5Gb RAM.
> > > >
> > > > Doh. How does that compare to the all-CP2K in one file builds?
> > >
> > > an all-in-one-file-CP2K takes about 2.5Gb and 30min last time I tested. So it
> > > is mostly the memory increase that is really significant.
> >
> > Ok, that's interesting. I'm curious if compiling all-in-one CP2K with
> > -flto is any different.
>
> -flto wit hthe all-in-one CP2K fails, I guess it enable -fwhole-file
> automatically ? Since it looks like the same error:
Yes, indeed it automatically enables -fwhole-file.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41069