This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Bug Digest 5/16
- From: "Giovanni Bajo" <giovannibajo at libero dot it>
- To: <gcc-bugs at gcc dot gnu dot org>,"Dara Hazeghi" <dhazeghi at yahoo dot com>
- Cc: "Wolfgang Bangerth" <bangerth at ices dot utexas dot edu>
- Date: Sat, 17 May 2003 09:10:52 +0200
- Subject: Re: Bug Digest 5/16
- References: <E303F244-8815-11D7-9A91-000393681B36@yahoo.com>
Dara Hazeghi <dhazeghi@yahoo.com> wrote:
> Hello,
>
> here are a couple that can be updated
Done. Thanks as always!
Exceptions:
> Close
> 8971 (submitter says this can be closed)
Where does he say so? If it was a private mail, would you please forward it
to the audit trail?
> 5256
Appears to be locked by Wolfgang (?).
> Suggestions for what to do?
> 9382 - not sure whether this is a latent bug in current gcc, or in old
> gcc.
I asked for a feedback about the attacched testcase. Did you try to compile
the attacched preprocessed source code with your fully-built cross-compilers
on AIX?
> 7126 - would just a patch adjusting the version # be enough?
I have no clue. Try submitting such a patch to gcc-patches, ask if it's ok
for mainline, and specify in the subject that it also fixes PR7126. After
you do so, mail to the audit trail of the PR a link to your mail (within the
gcc.gnu.org archive of course), so that it will not get forgot in case you
don't get a quick response.
> 4605 - is this a bug? Or just a misuse of shell quoting. I assume you
> can't have slashes in filenames, but...
He has a space in the directory name, not a slash. It should work and I'm
actually surprised to see it fails. Not sure what to do, can you reproduce
this?
Giovanni Bajo