This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/30376] aspell-0.60.5 fails to build with -O3 on gcc-4.1.2 20061222 (prerelease)
- From: "chris2553 at googlemail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jan 2007 05:56:29 -0000
- Subject: [Bug c++/30376] aspell-0.60.5 fails to build with -O3 on gcc-4.1.2 20061222 (prerelease)
- References: <bug-30376-13550@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from chris2553 at googlemail dot com 2007-01-05 05:56 -------
Subject: Re: aspell-0.60.5 fails to build with -O3 on gcc-4.1.2 20061222
(prerelease)
Thanks for the reply.
On Thursday 04 January 2007 22:25, pinskia at gcc dot gnu dot org wrote:
>
> ------- Comment #1 from pinskia at gcc dot gnu dot org 2007-01-04 22:25 -------
> > If I change the optimisation to -O2, the build completes, so I guess I have a
> > GCC problem.
>
> No, not always. In fact what most likely happening is something is being
> inlined (because of -O3) which was not before and now you get a reference to
> something which was not being referenced before.
>
Sorry, I simply don't understand that. The build completes with -O2 but not
with -O3. I'm light years away from even a basic knowledge of compiler
technology, but I would have thought that if the compiler inlined something,
there would be no reference for the linker to subsequently resolve. But, like I
say, I'm light years...
Anyway, since filing the bug report, I've built the package on my laptop, which
has GCC 3.3.6 installed. In this case the build completes with -O3
optimisation.
> I think the only way to fix this is to dig into the sources of aspell and see
> if this is the case. We cannot help that much except maybe do the compile for
> you.
If I was a C++ programmer, I might just do that. Unfortunately, I'm not! I did
have a dabble with Borland C++ many years ago, but since then templates (and
similar stuff) have been introduced and made the language too complex for me to
be bothered..
>
> It might be worth filing a bug with aspell and seeing what they can do with it.
>
>
That was my first port of call, but I got no response.
(http://lists.gnu.org/archive/html/aspell-user/2006-12/msg00012.html)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30376