--- Comment #7 from pinskia at gcc dot gnu dot org 2006-04-02 06:17 ---
http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01747.html
That points out what caused it and how it was fixed and it was not a GCC bug
after all so closing as invalid.
--
pinskia at gcc dot gnu dot org changed:
--- Comment #6 from rankincj at yahoo dot com 2006-04-01 23:00 ---
Subject: Re: Compile/link failure with -frepo and g++ 4.1
--- pinskia at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote:
> Well if you read the instructions on how to report a bug, a tar file is not
> really liked :).
A
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-03-31 00:32 ---
Well if you read the instructions on how to report a bug, a tar file is not
really liked :).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26922
--- Comment #4 from rankincj at yahoo dot com 2006-03-29 23:44 ---
Subject: Re: Compile/link failure with -frepo and g++ 4.1
--- pinskia at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote:
> Can you try a GCC which was released by the FSF and not a redhat modified one?
> If it works ther
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-03-29 23:22 ---
Can you try a GCC which was released by the FSF and not a redhat modified one?
If it works there, please report this to Redhat. Note this should have been
reported first to redhat and not here since you are using a
--- Comment #2 from rankincj at yahoo dot com 2006-03-29 21:10 ---
The sample code works OK with the following compilers:
$ g++ -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info
--enable-share
--- Comment #1 from rankincj at yahoo dot com 2006-03-29 15:36 ---
Created an attachment (id=11153)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11153&action=view)
Source code to demonstrate -frepo failure.
My host machine is a i686-pc-linux-gnu machine; g++-3.4.4 compiles this j
