This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: g++ bug
- To: Alex Taylor <ataylor at ihug dot com dot au>
- Subject: Re: g++ bug
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 13 Jul 2000 18:04:50 -0300
- Cc: gcc-bugs at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <396C42EE.76AFE7A3@ihug.com.au>
On Jul 12, 2000, Alex Taylor <ataylor@ihug.com.au> wrote:
> I can't send the .i files, because I don't have access to such a
> system, but can only give you the output my users are sending me.
Then please ask your users to send you the preprocessed output to you,
so that you can send it to us or maybe understand what it is that your
program is doing wrong. It is very unlikely that this is somehow
related with AMD chips; it's more likely to be related with some
particular release of g++ or some particular GNU/Linux distribution
(assuming that's the platform on which the problem has shown up).
Without this information, there's very little we can do.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me