Re: Bug Digest 5/16

[Dara Hazeghi <dhazeghi at yahoo dot com>]

Hello,

> > 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?

Done. Turns out to have been an issue covered by
"target specific config stuff."
> 
> > 5256
> 
> Appears to be locked by Wolfgang (?).

I'm not sure what you mean by "locked."

> 
> > 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?

Yes. As noted in the audit trail, it worked fine for
me. However, as John noted, his experience of the
problem depends on what is used for a bootstrap
compiler.

> 
> > 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.

Okay, when I get the chance...
> 
> > 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?

No, I can't reproduce this. Yeah, I misread it the
first time, but it appears to work fine here. That one
should go into feedback then (I sent a message)

In addition, here are a couple more changes:
Close:
10764

Mark as enhancement request or close (another solaris
/bin/sh issue) or close:
10811

Dara

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com